Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions 7 Doc/reference/import.rst
Original file line number Diff line number Diff line change
Expand Up @@ -464,8 +464,11 @@ import machinery will create the new module itself.

.. versionchanged:: 3.5
A :exc:`DeprecationWarning` is raised when ``exec_module()`` is defined but
``create_module()`` is not. Starting in Python 3.6 it will be an error to not
define ``create_module()`` on a loader attached to a ModuleSpec.
``create_module()`` is not.

.. versionchanged:: 3.6
An :exc:`ImportError` is raised when ``exec_module()`` is defined but
``create_module`` is not.

@berkerpeksag berkerpeksag Feb 26, 2017

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess create_module should be create_module() here since the latter form is also used in the first versionchanged note.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching this, @berkerpeksag! I fixed it in GH-325


Submodules
----------
Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.