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 eric.snow
Recipients brett.cannon, eric.snow
Date 2012-08-18.06:17:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ah, __import__() is used all over the place in the stdlib.  I won't have time right away to put together the patch then.  However, here's what I'm planning:

* expose builtin___import__() (from Python/bltinmodule.c) as imp.__import__().
* expose one used by the interpreter as builtins.__import__(), thus keeping it replaceable.
* hide it in <module globals>.__builtins__.

That last part is the tricky part, and has a bit of a smell to it...  Simply removing it from builtins would be easiest, but that still seems like the right place to go when you want to replace it with your own flashy __import__().

Insight appreciated, but this is definitely low priority at least for the next few months.
Date User Action Args
2012-08-18 06:17:56eric.snowsetrecipients: + eric.snow, brett.cannon
2012-08-18 06:17:56eric.snowsetmessageid: <>
2012-08-18 06:17:55eric.snowlinkissue15720 messages
2012-08-18 06:17:55eric.snowcreate