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 terry.reedy
Recipients brett.cannon, terry.reedy
Date 2013-08-31.21:35:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377984954.13.0.930666607286.issue18831@psf.upfronthosting.co.za>
In-reply-to
Content
Looking at the actual doc:
"importlib.__import__(name, globals=None, locals=None, fromlist=(), level=0) An implementation of the built-in __import__() function."

I think this is pretty clear that builtin.__import__ has no effect unless directly called.

"importlib.import_module(name, package=None)...The import_module() function acts as a simplifying wrapper around importlib.__import__()."

The word 'wrapper' implies that import_module calls __import__, but you say it currently does not. So if you want to keep the code as is, I would change 'acts as a simplifying wrapper around' to 'is a simplified version of', which makes no promises.

Do you really want people to directly call importlib.__import__? If not, maybe the nearly empty entry should be deleted and the entry for import_module changed to make no reference to it.
History
Date User Action Args
2013-08-31 21:35:54terry.reedysetrecipients: + terry.reedy, brett.cannon
2013-08-31 21:35:54terry.reedysetmessageid: <1377984954.13.0.930666607286.issue18831@psf.upfronthosting.co.za>
2013-08-31 21:35:54terry.reedylinkissue18831 messages
2013-08-31 21:35:53terry.reedycreate