Issue #19392: Document that imp.reload() now relies on __loader__

being defined on top of __name__.
This commit is contained in:
Brett Cannon 2013-10-25 13:46:15 -04:00
parent a4f6b006e1
commit 6fd25c39c4
2 changed files with 7 additions and 0 deletions

View File

@ -172,6 +172,10 @@ This module provides an interface to the mechanisms used to implement the
the class does not affect the method definitions of the instances --- they the class does not affect the method definitions of the instances --- they
continue to use the old class definition. The same is true for derived classes. continue to use the old class definition. The same is true for derived classes.
.. versionchanged:: 3.3
Relies on both ``__name__`` and ``__loader__`` being defined on the module
being reloaded instead of just ``__name__``.
The following functions are conveniences for handling :pep:`3147` byte-compiled The following functions are conveniences for handling :pep:`3147` byte-compiled
file paths. file paths.

View File

@ -531,6 +531,9 @@ Tests
Documentation Documentation
------------- -------------
- Issue #19392: Document that `imp.reload()` now also requires `__loader__` to
be set on the module being reloaded.
- Issue #18758: Fixed and improved cross-references. - Issue #18758: Fixed and improved cross-references.
- Issue #18743: Fix references to non-existant "StringIO" module. - Issue #18743: Fix references to non-existant "StringIO" module.