What would be the advantage of having it in the stdlib? It would put a stop on further development once it's been released as such, which strike me as a bad idea for a heuristic tool like 3to2. I would expect that you will continue to add more rules (and more exceptions) to it for the foreseeable future. You'll probably want to continue to maintain it as a 3rd party library so you can release those rules easily. Sounds like a bad idea to put it also in the stdlib, since you can't effectively update the stdlib version.
--Guido On Sun, Feb 21, 2010 at 1:00 PM, Joe Amenta <ament...@msu.edu> wrote: > Hey folks, > I'm going to write a PEP for inclusion of lib3to2 in the standard library > for 3.2 and above. Before do, though, do people have any quick thoughts > about it? > My inclination is to get it stabilized beforehand (perhaps during another > GSoC) by fleshing out the fixer that warns about backwards-incompatible > features in Python 3 and by finishing up the fix_imports2 fixer, probably > involving a rewrite. > http://bitbucket.org/amentajo/lib3to2 is where the source is hosted (there's > a separate branch for 3.1) > http://www.startcodon.com/wordpress/?cat=8 is where I blog about it. > http://pypi.python.org/pypi/3to2 is the PyPI page that has both of those > links. > --Joe Amenta > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > > -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
