Re: Python 2.2 support

2006-02-02 Thread Graham Dumpleton
On 03/02/2006, at 4:48 AM, Daniel J. Popowich wrote: My gut says any major release of mod_python be based on one major.minor release lower than the currently available python. So, mod_python 3.2 is based on python 2.3; mod_python 3.3 will probably be based on python 2.4 (because 2.5 will be out

Re: Python 2.2 support

2006-02-02 Thread Daniel J. Popowich
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 paragrap

Re: Python 2.2 support

2006-02-02 Thread Nicolas Lehuen
I am hereby happy to tell you that by removing the call to enumerate() in the publisher code, the whole test suite passes on Python 2.2 without any further patch or hack. I've checked in the modification which this time should not pose any problem since it's pretty basic and non intrusive. Regards

Re: Python 2.2 support

2006-02-01 Thread Graham Dumpleton
On 02/02/2006, at 5:42 PM, Nicolas Lehuen wrote: That's it ! People with Python 2.2 could use "PythonImport mod_python.python22 INTERPRETER_NAME" in their configuration file to make sure mod_python supports Python 2.2. The only problem is the need to provide an interpreter name, which complicat

Re: Python 2.2 support

2006-02-01 Thread Nicolas Lehuen
2006/2/2, Graham Dumpleton <[EMAIL PROTECTED]>: > Nicolas Lehuen wrote .. > > 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. > > I plead dumb. What is the

Re: Python 2.2 support

2006-02-01 Thread Graham Dumpleton
Nicolas Lehuen wrote .. > 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. I plead dumb. What is the connection to PythonImport? My only guess at the moment is

Re: Python 2.2 support

2006-02-01 Thread Nicolas Lehuen
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]>: > >

Re: Python 2.2 support

2006-02-01 Thread Nicolas Lehuen
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 impressi

Re: Python 2.2 support

2006-02-01 Thread Jim Gallacher
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. The

Re: Python 2.2 support

2006-02-01 Thread Nicolas Lehuen
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 : Consi

Re: Python 2.2 support

2006-02-01 Thread Daniel J. Popowich
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 pret

Re: Python 2.2 support

2006-02-01 Thread Jim Gallacher
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 lat

Re: Python 2.2 support

2006-02-01 Thread Jamie Bliss
On 2/1/06, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > 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 vers

Re: Python 2.2 support

2006-02-01 Thread Graham Dumpleton
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