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 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 there was never really a discussion on this issue. > > Some 2.3-isms got used, so it was decided that 2.2 was not supported. > > There likely should have been a more formal discussion on whether this > > is right time to drop 2.2 support. Certainly we haven't done any testing > > using python 2.2 so even with the hack I don't think we can comfortably > > claim that that version is supported. > > Note that I have ran successfully the unit tests on Python 2.2, 2.3 > and 2.4 before checking this hack in. Granted, this is not a guarantee > that Python 2.2 is supported, but given our tests coverage, this is > pretty good. > > Regards, > Nicolas >
