|
From: Craeg S. <cs...@ar...> - 2003-06-08 22:50:08
|
> Craeg Strong wrote: > > Thanks for the information! > > > > You have found an innovative solution > > to the problem that Zope currently does not > > support Python 2.2, while the latest libxslt uses it! > > Does it? I can't see where it *requires* it. I believe it is purely an installation issue for win32. I think it looks for python 2.2 in the registry. I dunno, I haven't really tried it. If the latest releases of libxslt *do* work with python 2.1.x, they sure don't advertise it... > > > I have heard rumors that the next point release of > > Zope 2.6 will support Python 2.2, and that would > > likely be available in the next 1-3 months. > > There are still a lot of problems with Zope 2.X and Python 2.2, even in > 2.7. For example, starting with Python 2.2, builtin types have > docstrings, thus the ZPublisher can publish them. While everyone agrees > that the ZPublisher's policy of using the docstring is stupid, the > problem remains. Actually, according to recent traffic on zope-dev this problem was recently fixed IIRC. Further, the fix may have happened in the 2.6.X branch. We may yet get Python 2.2 support in the near future! > I believe 2.1 is currently the best platform for Zope 2. Agreed. Sigh. > Philipp > > P.S.: I can't see any advancements on the XSLT parameters issue. I have > safely arrived in Mexico and have some time now. Do you guys still want > me to tackle this problem? > Yes, Please :) --Craeg |
