> [..] > > the situation as is is a PITA. > > Not _requiring_ the newest version of Python is not that bad, > but _breaking_ on newer versions of Python is a PITA indeed.
well, although not requiring is not that bad, there is special interest in using 2.5 as there are a few serious issues fixed, like the GC one. > OTOH, as an outsider to Zope development, i dare not judge > what additional work load support for multiple Python versions > per Zope version might entail... > In my smaller Python projects, avoiding deprecated constructs > and planning for future upward compatibility was not an issue, > but Zope is a gigantic and convoluted beast indeed. afaik, zope3 already works with 2.5. 2.5 support for zope2 is scheduled for the 2008 GSOC afaik.. we'll see. f.-
