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

[Petri Lehtinen]

Petri Lehtinen  added the comment:

Fixed, thanks for the patch.

BTW, you should sign the PSF Contributor Agreement. See 
http://www.python.org/psf/contrib/.

--
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Roundup Robot]

Roundup Robot  added the comment:

New changeset cc9e5ddd8220 by Petri Lehtinen in branch '2.7':
#14494: Document that absolute imports became default in 3.0 instead of 2.7.
http://hg.python.org/cpython/rev/cc9e5ddd8220

New changeset 7cdc1392173f by Petri Lehtinen in branch '3.2':
#14494: Document that absolute imports became default in 3.0 instead of 2.7.
http://hg.python.org/cpython/rev/7cdc1392173f

New changeset 26661d9bbb36 by Petri Lehtinen in branch 'default':
#14494: Document that absolute imports became default in 3.0 instead of 2.7.
http://hg.python.org/cpython/rev/26661d9bbb36

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Petri Lehtinen]

Changes by Petri Lehtinen :


--
nosy: +petri.lehtinen

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Eric Snow]

Changes by Eric Snow :


--
nosy: +eric.snow

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[R. David Murray]

Changes by R. David Murray :


--
stage:  -> patch review
versions:  -Python 2.6, Python 3.1

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Sven Marnach]

New submission from Sven Marnach :

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@python
components: Documentation, Library (Lib)
files: absolute_import.patch
keywords: patch
messages: 157474
nosy: docs@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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com