Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
2fc6181a
Commit
2fc6181a
authored
Oct 25, 2013
by
Brett Cannon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Issue #19392: Document that imp.reload() now relies on __loader__
being defined on top of __name__.
parent
20b4d6f5
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
0 deletions
+7
-0
Doc/library/imp.rst
Doc/library/imp.rst
+4
-0
Misc/NEWS
Misc/NEWS
+3
-0
No files found.
Doc/library/imp.rst
View file @
2fc6181a
...
...
@@ -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
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
file paths.
...
...
Misc/NEWS
View file @
2fc6181a
...
...
@@ -531,6 +531,9 @@ Tests
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 #18743: Fix references to non-existant "StringIO" module.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment