A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-February/116313.html below:

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

[Python-Dev] requirements for moving __import__ over to importlib? [Python-Dev] requirements for moving __import__ over to importlib?Brett Cannon brett at python.org
Wed Feb 8 17:16:24 CET 2012
On Tue, Feb 7, 2012 at 18:26, Alex Gaynor <alex.gaynor at gmail.com> wrote:

> Brett Cannon <brett <at> python.org> writes:
>
>
> > 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.
> >
>
>
> Sure you can: have a really fast Python VM.
>
> Constructive: if you can run this code under PyPy it'd be easy to just:
>
> $ pypy -mtimeit "import struct"
> $ pypy -mtimeit -s "import importlib" "importlib.import_module('struct')"
>
> Or whatever the right API is.


I'm not worried about PyPy. =) I assume you will just  flat-out use
importlib regardless of what happens with CPython since it is/will be fully
compatible and is already written for you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120208/531f15b6/attachment.html>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4