This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author memeplex
Recipients docs@python, memeplex
Date 2015-10-29.12:06:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446120404.56.0.248022316134.issue25509@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation (for 3.5) states that "[PyImport_ImportModule] is a simplified interface to PyImport_ImportModuleEx()" but the current implementation calls PyImport_Import instead, which is a higher level interface that takes into account import hooks. Older versions of PyImport_ImportModule (say 2.0) did call PyImport_ImportModuleEx, but that's no longer the case.

The PyImport_Import* naming convention got a bit messy with the years and maybe I'm not understanding the intention quite well, but it seems to me that the documentation is outdated and that there is a change in semantics for PyImport_ImportModule.
History
Date User Action Args
2015-10-29 12:06:44memeplexsetrecipients: + memeplex, docs@python
2015-10-29 12:06:44memeplexsetmessageid: <1446120404.56.0.248022316134.issue25509@psf.upfronthosting.co.za>
2015-10-29 12:06:44memeplexlinkissue25509 messages
2015-10-29 12:06:43memeplexcreate