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 connection to PythonImport? > > My only guess at the moment is that it does something like I do in my > new importer, which is to use PythonImport to import a module which goes > in and fiddles with the contents of mod_python.apache/publisher to patch > in my new code before any request handlers get a chance to be called. > In this way I don't have to be patching the actual mod_python source code. > > Graham
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 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. Regards, Nicolas
