[docs] [issue15482] __import__() change between 3.2 and 3.3

Nick Coghlan report at bugs.python.org
Sun Jul 29 05:35:00 CEST 2012

Nick Coghlan added the comment:

The specific bug is that, in 3.2, the claimed default (level=0) is not accurate: the default is actually (level=-1), as it was in 2.x. The import statement passes level=0 explicitly (as it does in 2.x when "from __future__ import absolute_import" is in effect).

The docstring in 3.2 is accurate, the prose documentation is incorrect.

In 3.3, the docstring is currently wrong, but the prose documentation is correct. However, it should have a "versionchanged: 3.3" not added, indicating that the default import level has finally been brought into compliance with the documentation.


Python tracker <report at bugs.python.org>

More information about the docs mailing list