#24081: Remove obsolete caveat from import docs.
Per Eric Snow's research, this changed in Python 2.4 in changeset 331e60d8ce, but these docs were not updated. Patch by Peter Viktorin.
This commit is contained in:
parent
c6249a6268
commit
6d877ef026
|
@ -149,12 +149,6 @@ This module provides an interface to the mechanisms used to implement the
|
|||
|
||||
There are a number of other caveats:
|
||||
|
||||
If a module is syntactically correct but its initialization fails, the first
|
||||
:keyword:`import` statement for it does not bind its name locally, but does
|
||||
store a (partially initialized) module object in ``sys.modules``. To reload the
|
||||
module you must first :keyword:`import` it again (this will bind the name to the
|
||||
partially initialized module object) before you can :func:`reload` it.
|
||||
|
||||
When a module is reloaded, its dictionary (containing the module's global
|
||||
variables) is retained. Redefinitions of names will override the old
|
||||
definitions, so this is generally not a problem. If the new version of a module
|
||||
|
|
|
@ -152,12 +152,6 @@ Functions
|
|||
|
||||
There are a number of other caveats:
|
||||
|
||||
If a module is syntactically correct but its initialization fails, the first
|
||||
:keyword:`import` statement for it does not bind its name locally, but does
|
||||
store a (partially initialized) module object in ``sys.modules``. To reload
|
||||
the module you must first :keyword:`import` it again (this will bind the name
|
||||
to the partially initialized module object) before you can :func:`reload` it.
|
||||
|
||||
When a module is reloaded, its dictionary (containing the module's global
|
||||
variables) is retained. Redefinitions of names will override the old
|
||||
definitions, so this is generally not a problem. If the new version of a
|
||||
|
|
Loading…
Reference in New Issue