[Python-Dev] importlib is now bootstrapped (and what that means)

Eric V. Smith eric at trueblade.com
Fri Apr 20 17:07:32 CEST 2012

On 04/20/2012 10:59 AM, Brett Cannon wrote:
> On Fri, Apr 20, 2012 at 09:54, Eric V. Smith <eric at trueblade.com
> <mailto:eric at trueblade.com>> wrote:
>     On 04/14/2012 02:12 PM, Brett Cannon wrote:
>     > My multi-year project -- started in 2006 according to my blog -- to
>     > rewrite import in pure Python and then bootstrap it into CPython as
>     > *the* implementation of __import__() is finally over (mostly)!
>     Maybe I'm missing something, but it seems that I need to run
>     importlib._bootstrap._install(sys, _imp) manually in order to make
>     __import__ be importlib's version. Is that not supposed to happen
>     automatically?
> It's happening automatically. If you look in Python/import.c you will
> notice that the code that __import__() eventually calls is calling out
> into the Python code. There is still some C code in order to accelerate
> the case of hitting sys.modules.

Okay. But I'm running make, and that's succeeding (and it looks like it
does the right thing), yet it doesn't appear to be picking up my changes
to _bootstrap.py automatically. I'll keep investigating.


More information about the Python-Dev mailing list