[Python-Dev] requirements for moving import over to importlib? (original) (raw)
Brett Cannon brett at python.org
Wed Feb 8 17:01:35 CET 2012
- Previous message: [Python-Dev] requirements for moving __import__ over to importlib?
- Next message: [Python-Dev] requirements for moving __import__ over to importlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Feb 7, 2012 at 17:42, Antoine Pitrou <solipsis at pitrou.net> wrote:
On Tue, 7 Feb 2012 17:24:21 -0500 Brett Cannon <brett at python.org> wrote: > > IOW you want the sys.modules case fast, which I will never be able to match > compared to C code since that is pure execution with no I/O.
Why wouldn't continue using C code for that? It's trivial (just a dict lookup).
Sure, but it's all the code between the function call and hitting sys.modules which would also need to get shoved into the C code. As I said, I have not tried to optimize anything yet (and unfortunately a lot of the upfront costs are over stupid things like checking if import is being called with a string for the module name). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120208/bceefd98/attachment-0001.html>
- Previous message: [Python-Dev] requirements for moving __import__ over to importlib?
- Next message: [Python-Dev] requirements for moving __import__ over to importlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]