[Python-Dev] requirements for moving __import__ over to importlib?

Brett Cannon brett at python.org
Wed Feb 8 17:15:14 CET 2012

On Tue, Feb 7, 2012 at 22:47, Nick Coghlan <ncoghlan at gmail.com> wrote


> The fact that we have an undocumented PEP 302 based reimplementation
> of imports squirrelled away in pkgutil to make pkgutil and runpy work
> is sheer insanity (replacing *that* with importlib might actually be a
> good first step towards full integration).

It easily goes beyond runpy. You could ditch much of imp's C code (e.g.
load_module()), you could write py_compile and compileall using importlib,
you could rewrite zipimport, etc. Anything that touches import could be
refactored to (a) use just Python code, and (b) reshare code so as to not
re-invent the wheel constantly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120208/aac12505/attachment.html>

More information about the Python-Dev mailing list