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-30.23:04:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377903890.8.0.592678900504.issue18831@psf.upfronthosting.co.za>
In-reply-to
Content
Perhaps I am confused because I did not notice the switch between builtins.__import__ and importlib.__import__ -- and I do not know the relation between the two, if indeed they are two and not one. What I read and understood is
* importlib.import_module doc say it calls ???.__import__;
* importlib.import_module code does not call ???.__import__;
it instead calls _gcd_import (for good reasons).

If the claim and reality disagree, because ??? is effectively the same in both statements, then either code or doc could be changed.

If importlib.__import__ and builtins.__import__ are different objects, and the doc is clear about that, then no one should expect that 'calls importlib.__import__' means 'calls builtins.__import__'.
History
Date User Action Args
2013-08-30 23:04:50terry.reedysetrecipients: + terry.reedy, brett.cannon
2013-08-30 23:04:50terry.reedysetmessageid: <1377903890.8.0.592678900504.issue18831@psf.upfronthosting.co.za>
2013-08-30 23:04:50terry.reedylinkissue18831 messages
2013-08-30 23:04:50terry.reedycreate