Hi Marc, Marc Balmer wrote on, May 12, 2008 at 09:42:55PM +0200:
> we should really begin to tell the zope people Well, the last time we tried to talk to them was not exactly a success. ;) > to begin using recent python versions for zope. Let's have a quick look at the timeline: Jul 29, 2003: Python 2.3 release Jul 8, 2004: Python 2.4 alpha 1 Nov 30, 2004: Python 2.4 release Jun 4, 2005: Zope 2.8 release requiring Python 2.3 (2/11 months) Oct 2, 2005: Zope 3.1 release requiring Python 2.4 (last available) Dec 5, 2005: Zope 3.2 release requiring Python 2.4 (last available) Jan 7, 2006: Zope 2.9 release requiring Python 2.4 (last available) Apr 5, 2006: Python 2.5 alpha 1 Sep 19, 2006: Python 2.5 release Sep 27, 2006: Zope 3.3 release requiring Python 2.4 (0/5 months) Oct 3, 2006: Zope 2.10 release requiring Python 2.4 (0.5/6 months) Nov 5, 2007: Zope 3.4 beta 2 requiring Python 2.4 (13/19 months) Dec 28, 2007: Zope 2.11 beta 1 requiring Python 2.4 (15/20 months) Feb 29, 2008: Python 2.6 alpha 1 Sep 03, 2008: Python 2.6 release scheduled (PEP 361) So, the Zope people used to be typically 0 to 2 months behind - or 0 to 11 months if you argue that Python alpha releases are good enough to do compatibility testing. Perhaps, watching out for deprecation notices in PEPs might provide even earlier clues. But there does seem to be a problem recently concerning the adoption of Python 2.5, both in the 2.11 and 3.4 branches. > 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. 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. Yours, Ingo
