[issue14494] __future__.py and its documentation claim absolute imports became mandatory in 2.7, but they didn't

Sven Marnach report at bugs.python.org
Wed Apr 4 14:53:06 CEST 2012


New submission from Sven Marnach <sven at marnach.net>:

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.

[1]: http://article.gmane.org/gmane.comp.python.devel/125446

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.

----------
assignee: docs at python
components: Documentation, Library (Lib)
files: absolute_import.patch
keywords: patch
messages: 157474
nosy: docs at python, smarnach
priority: normal
severity: normal
status: open
title: __future__.py and its documentation claim absolute imports became mandatory in 2.7, but they didn't
type: behavior
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file25118/absolute_import.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14494>
_______________________________________


More information about the Python-bugs-list mailing list