On 3/12/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On 3/12/07, Collin Winter <[EMAIL PROTECTED]> wrote: > > On 3/12/07, Tony Lownds <[EMAIL PROTECTED]> wrote: > > > Cool. Out of curiosity, what versions of Python should 2to3 need to > > > run? I know that 2to3/refactor.py needs 2.3 < Python < 3.0. Guess which > > > versions I have handy :) > > > > I use 2.5. 2.3 and 2.4 both fail the test suite, bailing out with > > SyntaxErrors in various places. > > I think that if it becomes a requirement it shouldn't be too hard to > make the refactoring tool work with older versions though, up to 2.2. > but we should determine need first.
As of r54311, 2to3 now works with Python 2.4. I tried making it work with Python 2.3, but it's going to require changes wrt. how 2to3 interacts with the logging module, and I don't know enough about logging to know what needs to change. > > > Also, since I believe sys.exc_info() is staying, fix_sysexcinfo > > > should change... > > > > Right. It's already on my todo list. > > I must've missed that. What happened? I thought the decision had been made (or at least, the consensus reached) that sys.exc_info() would stick around in Python 3. Collin Winter _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com