Movatterモバイル変換
[0]ホーム
[Python-Dev] requirements for moving __import__ over toimportlib?
Brett Cannonbrett at python.org
Wed Feb 8 17:28:31 CET 2012
On Wed, Feb 8, 2012 at 11:15, Brett Cannon <brett at python.org> wrote:>>> On Tue, Feb 7, 2012 at 22:47, Nick Coghlan <ncoghlan at gmail.com> wrote>> [SNIP]>>>> 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.>And taking it even farther, all of the blackbox aspects of import go away.For instance, the implicit, hidden importers for built-in modules, frozenmodules, extensions, and source could actually be set on sys.path_hooks.The Meta path importer that handles sys.path could actually exist onsys.meta_path.-------------- next part --------------An HTML attachment was scrubbed...URL: <http://mail.python.org/pipermail/python-dev/attachments/20120208/cde68be8/attachment.html>
More information about the Python-Devmailing list
[8]ページ先頭