#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.
diff --git a/Doc/library/imp.rst b/Doc/library/imp.rst
index c2dbdc5..83a52e4 100644
--- a/Doc/library/imp.rst
+++ b/Doc/library/imp.rst
@@ -149,12 +149,6 @@
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
diff --git a/Doc/library/importlib.rst b/Doc/library/importlib.rst
index 91328af..c947335 100644
--- a/Doc/library/importlib.rst
+++ b/Doc/library/importlib.rst
@@ -152,12 +152,6 @@
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