is the need
to provide an interpreter name, which complicates things a little bit
in the case of the test suite.
Then again, the only thing which prevents Python 2.2 support right now
is the use of enumerate(), so we could just check whether we could do
without enumerate() and support
Jim Gallacher writes:
Daniel J. Popowich wrote:
Regardless, I do not think it is within the scope of mod_python
developers to keep users forward-compatible with the underlying python
version. Sorry, but IMHO, this is not scalable software engineering.
I'll re-read this paragraph after
Again this is a resend. I post one message via my secure SMTP and it
vanishes. Post one via normal SMTP and it goes to list straight away.
This sort of confirms what I suspected which is that my ISPs secure
SMTP is busted somehow in that randomly drops email. :-(
Sorry for the duplicate if first
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
Nicolas Lehuen writes:
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
Quick response, because it's 4:36 AM here, I just woke up to feed my
daughter and took all this flak, but I need to sleep :). I guess
that's the problem of having a round-the-planet development team,
between those in America, Europe, Asia and Australia (nobody from
Antarctica yet ?)
Graham :
Daniel J. Popowich wrote:
Nicolas Lehuen writes:
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.
2006/2/2, Jim Gallacher [EMAIL PROTECTED]:
If a formal decision was made, then it's a done deal, right? If not
and uses of 2.3 have slipped in then perhaps it's a done deal anyway
because no one can stomach the thought of taking out the 2.3-isms at
this late date.
My impression is that
OK, I've reverted my changes. I left python22.py in place, because I
still hope to be able to use it with PythonImport. The only problem is
being able to define it in the unit tests.
Regards,
Nicolas
2006/2/2, Nicolas Lehuen [EMAIL PROTECTED]:
2006/2/2, Jim Gallacher [EMAIL PROTECTED]:
If a
to provide an interpreter name, which complicates things a little bit
in the case of the test suite.
Then again, the only thing which prevents Python 2.2 support right now
is the use of enumerate(), so we could just check whether we could do
without enumerate() and support Python 2.2 out of the box
10 matches
Mail list logo
