[issue1138] Fixer needed for __future__ imports

2007-11-30 Thread Christian Heimes
Christian Heimes added the comment: Fixed in r59235 It was easier to add a new fixer for the problem. -- nosy: +tiran resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue1138] Fixer needed for __future__ imports

2007-11-23 Thread Christian Heimes
Changes by Christian Heimes: -- keywords: +py3k versions: +Python 3.0 __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsub

[issue1138] Fixer needed for __future__ imports

2007-09-09 Thread Collin Winter
New submission from Collin Winter: Per http://mail.python.org/pipermail/python-3000/2007-September/010337.html, 2to3 should strip out __future__ imports. This should probably be added to the existing import fixer. -- assignee: collinwinter components: 2to3 (2.x to 3.0 conversion tool) me