[Neil McGovern, 2010-09-08] > I'm slightly worried by: > 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. > > and: > Note The lib2to3 API should be considered unstable and may change > drastically in the future.
once again, we are NOT going to add python3-foo binary packages for code not tested with Python 3 by upstream. I ask about packages for which upstream claims 2to3 did a good job or it wasn't needed at all. Adam: I uploaded my packages that support Python 3 (beaker and mako). Let me know if I will not waste my time and I will work on docutils, cython and lxml next. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
