This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author smarnach
Recipients docs@python, smarnach
Date 2012-04-04.12:53:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333543986.45.0.920300905324.issue14494@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012-04-04 12:53:06smarnachsetrecipients: + smarnach, docs@python
2012-04-04 12:53:06smarnachsetmessageid: <1333543986.45.0.920300905324.issue14494@psf.upfronthosting.co.za>
2012-04-04 12:53:05smarnachlinkissue14494 messages
2012-04-04 12:53:05smarnachcreate