Am 13.05.2008 um 00:18 schrieb Stuart Henderson:
On 2008/05/13 00:09, Ingo Schwarze wrote:
Jul 29, 2003: Python 2.3 release
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)
> [..]
> > 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
On 2008/05/13 00:09, Ingo Schwarze wrote:
> Jul 29, 2003: Python 2.3 release
> 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)
Sorry to break in on the thread, but something
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
also forced to still
run Zope 2.8 on 4.3 or -current (perhaps i should rather tell
the owner of that 2.8 site to either fix his plugins to work
with 2.9 or to go to hell...)
This is a quick backport of Marc Balmer's zope-2.9.8 port
to zope 2.8.9.1. To make it build, you must move ../Makefil
rent (perhaps i should rather tell
the owner of that 2.8 site to either fix his plugins to work
with 2.9 or to go to hell...)
This is a quick backport of Marc Balmer's zope-2.9.8 port
to zope 2.8.9.1. To make it build, you must move ../Makefile.inc
aside. Agreed, that's not a clean way, but
