[issue4271] conversion tool does not fix "from Tkinter import N,E"

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: The other problem is fixed in r67170. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> __

[issue4271] conversion tool does not fix "from Tkinter import N,E"

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: -> high ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list

[issue4271] conversion tool does not fix "from Tkinter import N,E"

Winfried Plappert <[EMAIL PROTECTED]> added the comment: Sorry, issue 1 still persists: >From Tkinter import (bla,blah, blahh) ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4271] conversion tool does not fix "from Tkinter import N,E"

Winfried Plappert <[EMAIL PROTECTED]> added the comment: and it is also fixed in 3.0rc1: I reran the conversion, but issue 2 still persists, ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue4271] conversion tool does not fix "from Tkinter import N,E"

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: The relative import problem has been fixed that will be released in 2.6.1. -- nosy: +benjamin.peterson type: compile error -> behavior ___ Python tracker <[EMAIL PROTECTED]>

[issue4271] conversion tool does not fix "from Tkinter import N,E"

New submission from Winfried Plappert <[EMAIL PROTECTED]>: I tried to check the tracker for an existing issue with the conversion tool, but I could not find one. I am using the "python2.6 Python2.6/Tools/scripts/2to3 -w -v ." command to convert existing Python scripts to Python3.0. I made two ob