You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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=Noneclosed_at=<Date2012-05-19.15:47:50.767>created_at=<Date2012-04-04.12:53:05.844>labels= ['type-bug', 'library', 'docs']
title="__future__.py and its documentation claim absolute imports became mandatory in 2.7, but they didn't"updated_at=<Date2012-05-19.15:47:50.766>user='https://github.com/smarnach'
As has been pointed out before on python-dev 1, the mandatory version of '__future__.absolute_import' does not match reality. In Python 2.7, absolute imports are not the default.
The attached patch should fix the documentation and Lib/future.py. I set the mandatory version to (3, 0, 0, "alpha", 0), in accordance with other features that became mandatory in Py3k, though there never was a 3.0a0 release. I double-checked that absolute imports already were the default in 3.0a1.
The patch should probably be applied to all branches.
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: