On Thu, Sep 09, 2010 at 11:25:30AM +0200, Matthias Klose wrote:
Sometimes 2to3 will find a place in your source code that needs to be
changed, but 2to3 cannot fix automatically. In this case, 2to3 will
print a warning beneath the diff for a file. You should address the
warning in order to have compliant 3.x code.
so what? 2to3 will never be a tool which results should be used without inspection.
So if a patch comes out that fixes a security bug in foo.py(2), that is
incompatable with 2to3, then it needs fixing twice. Which is why I've
asked the secruity team for input.
and:
Note The lib2to3 API should be considered unstable and may change
drastically in the future.
wrong. lib2to3 in python2.6 is stable.
That was taken from: http://docs.python.org/library/2to3.html
Do you have further information? A reference would certainly be useful.