[issue19111] 2to3 should remove from future_builtins import *

Change by Irit Katriel : -- resolution: -> wont fix stage: -> resolved status: open -> closed superseder: -> Close 2to3 issues and list them here ___ Python tracker ___

[issue19111] 2to3 should remove from future_builtins import *

Josh Rosenberg added the comment: Ah, my mistake. Apologies. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19111 ___ ___ Python-bugs-list

[issue19111] 2to3 should remove from future_builtins import *

Josh Rosenberg added the comment: Shouldn't it also disable the relevant fixers for map, filter, zip, etc. as appropriate? Otherwise a whole bunch of calls will be wrapper in list() or the like to mimic a behavior the code never had in Py2 in the first place. -- nosy: +josh.r

[issue19111] 2to3 should remove from future_builtins import *

Milan Oberkirch added the comment: The other fixers you mentioned are deactivated independently of this patch if an import from future_builtins exists. I gave it the same run_order as in the fix for __future__ imports which prevents 2to3 from deleting the calls before other fixers check for

[issue19111] 2to3 should remove from future_builtins import *

Milan Oberkirch added the comment: Here is a simple patch that would solve this issue. The new fixer 'future_builtins' removes `from future_builtins import foo` statements if they aren't nested in other constructs (try-except, classes, ...) and replaces them with `pass` otherwise. --

[issue19111] 2to3 should remove from future_builtins import *

Kevin Christopher Henry added the comment: I'm interested in working on this, but it's not clear to me if this has been accepted as a bug. I converted a large project recently and was shocked to find that all 100+ files were broken because of the needless from future_builtins... line.

[issue19111] 2to3 should remove from future_builtins import *

Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19111 ___ ___

[issue19111] 2to3 should remove from future_builtins import *

Peter added the comment: Thinking about this, perhaps the bug is that Python 3 doesn't have a future_builtins module? Consider: $ python2.6 Python 2.6.8 (unknown, Sep 28 2013, 12:09:28) [GCC 4.6.3] on linux3 Type help, copyright, credits or license for more information. from __future__

[issue19111] 2to3 should remove from future_builtins import *

New submission from Peter: The 2to3 script should remove lines like this: from future_builtins import zip after running the zip fixer which respects the meaning of this command (issue 217). It does not, which results in an ImportError when trying to use the converted code under Python 3.