Repository navigation
2to3 incorrectly handles multi-line imports from __future__ #57082
Description
| BPO | 12873 |
|---|---|
| Nosy | @benjaminp, @merwok |
| Superseder |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2021-10-20.22:46:23.585>
created_at = <Date 2011-08-31.21:57:20.653>
labels = ['expert-2to3']
title = '2to3 incorrectly handles multi-line imports from __future__'
updated_at = <Date 2021-10-20.22:46:23.584>
user = 'https://bugs.python.org/Arfrever'bugs.python.org fields:
activity = <Date 2021-10-20.22:46:23.584>
actor = 'iritkatriel'
assignee = 'none'
closed = True
closed_date = <Date 2021-10-20.22:46:23.585>
closer = 'iritkatriel'
components = ['2to3 (2.x to 3.x conversion tool)']
creation = <Date 2011-08-31.21:57:20.653>
creator = 'Arfrever'
dependencies = []
files = []
hgrepos = []
issue_num = 12873
keywords = []
message_count = 5.0
messages = ['143283', '143418', '143425', '143429', '253129']
nosy_count = 5.0
nosy_names = ['benjamin.peterson', 'eric.araujo', 'Arfrever', 'lunaryorn', 'jdekloe']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = 'resolved'
status = 'closed'
superseder = '45544'
type = None
url = 'https://bugs.python.org/issue12873'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3']
Activity
Arfrever commentedon Aug 31, 2011
$ cat test1.py from __future__ import (absolute_import, division, print_function, unicode_literals)merwok commentedon Sep 2, 2011
I don’t understand what the bug is.
Arfrever commentedon Sep 2, 2011
If import from __future__ is written in multiple lines, then a parser internally used by 2to3 recognizes only the first line. (However Python interpreter properly supports multi-line imports from __future__.)
test1.py contains multi-line import from __future__.
test2.py contains single-line import from __future__.
2to3 properly handles test2.py and improperly handles test1.py.
lunaryorn commentedon Sep 2, 2011
More precisely, the bug is, that 2to3 refactors the "print()" invocation in "test1.py" though it shouldn't because a "print_function" future import is present at the beginning of "test1.py". The cross-check with "test2.py" shows that this is due to the multi-line future import in "test1.py" because the line-break in the import statement is the only difference between both files.
jdekloe commentedon Oct 17, 2015
still having this issue with 2to3 from python-tools-2.7.8-11 as packaged by Fedora 21.
Any progress since 2011?