[issue3836] 2to3 broken due to mixed 2.5 and 3.0 syntax

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Fixed in r66392. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3836] 2to3 broken due to mixed 2.5 and 3.0 syntax

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: main.py is really not a public interface, but it should be fixed. -- assignee: collinwinter -> benjamin.peterson nosy: +benjamin.peterson priority: -> high ___ Python tracker <[EMAIL PROTECTED]

[issue3836] 2to3 broken due to mixed 2.5 and 3.0 syntax

Haoyu Bai <[EMAIL PROTECTED]> added the comment: A patch on main.py to fix this. -- keywords: +patch Added file: http://bugs.python.org/file11464/fix_syntax.diff ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3836] 2to3 broken due to mixed 2.5 and 3.0 syntax

New submission from Haoyu Bai <[EMAIL PROTECTED]>: In the py3k SVN head(r66389) of lib2to3, the main.py used Python 2.x's print syntax, and the refactor.py used Python 3.0's exception syntax. So the 2to3 finally broken on both Python 2.5 and 3.0. Well, it able to run with Python 2.6, but also ha