Author memeplex
Recipients brett.cannon, docs@python, memeplex
Date 2015-11-01.01:58:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446343138.26.0.104349348162.issue25509@psf.upfronthosting.co.za>
In-reply-to
Content
Brett, I'm not sure about that, notice that the "import hook" as is mentioned in the docs is just the current __import__ in the builtins module (which could have been replaced and in this sense would be a "hook") but not proper import hooks. I think the original distinction between PyImport_ImportModule and PyImport_Import is still sensible today. Originally PyImport_ImportModule directly called the import machinery, while PyImport_Import called it indirectly through builtins.__import__ (which could have been replaced). Now, for some reason, for good or for bad, PyImport_ImportModule also goes through builtins.__import__. The documentation is wrong but what is the fix? Revert PyImport_ImportModule or redocument it?
History
Date User Action Args
2015-11-01 01:58:58memeplexsetrecipients: + memeplex, brett.cannon, docs@python
2015-11-01 01:58:58memeplexsetmessageid: <1446343138.26.0.104349348162.issue25509@psf.upfronthosting.co.za>
2015-11-01 01:58:58memeplexlinkissue25509 messages
2015-11-01 01:58:56memeplexcreate