Graham Dumpleton wrote:
On 01/02/2006, at 9:10 PM, Nicolas Lehuen wrote:
Hi,
I've just checked in some changes to the Python source code in order
to support Python 2.2. Now the test suite runs successfully on Python
2.2.3 on Windows 2000. I've checked that no regressions were
introduced in later Python versions, too.
The changes are pretty simple : each Python module now features a
"from python22 import *". The mod_python.python22 module just
reimplements new builtins from Python 2.3. It turns out that the only
missing builtin for now is enumerate(). The tests module, containing a
few tests for generators, has to sport a "from __future__ import
generators" line.
Does that mean that 3.2.6 is now no more if you are checking stuff in and
we can't avoid a 3.2.7b?
Not necessarily. If 3.2.6 is good then it doesn't matter what is in
trunk. There is a 3.2.6 snapshop in tags/.
I think it's time to give 3.2 it's own svn branch so we *can* start
checking stuff into trunk again. If we do need to do a 3.2.7 release in
the near future it can come from the 3.2.x branch.
So, I propose creating a new "branches/3.2.x" svn branch today. Any
objections?
I understood the only Python 2.3 dependency to be the use of enumerate()
in mod_python.publisher. If that was true, why couldn't the one place be
changed rather than modifying all modules with this import?
I also had to change mod_python.cache which used time.strptime so that
it uses rfc822.parsedate, now.
Two things to change then.
I've did this because the guys from Nokia use Python 2.2 and
mod_python 3.1.3. They spotted memory leaks which are likely to be
fixed in mod_python 3.2.X, but they could not upgrade if Python 2.2
was not supported.
They are only one customer. I know they might be seen to be of high
interest because of the cool factor of what they have done, but should
we have really deferred doing a release because of it.
Sorry to be the release Nazi, but this really is starting to drag on. The
Python 2.2 backward compatibility changes could have been documented
in JIRA and people referred to that if they really wanted to make 3.2.6
work with that version of Python. :-(
I think it may have been a mistake to drop python 2.2 support just yet.
Aren't some RHAT enterprise systems still stuck at that python version?
I suspect we won't see this issue raised until *after* mp 3.2 is
released. Nicolas' patch python 2.2 patch can be backported to 3.2.x
branch for a bugfix release.
Jim
