[Python-Dev] importlib is now bootstrapped (and what that means) (original) (raw)
Eric V. Smith eric at trueblade.com
Fri Apr 20 17:07:32 CEST 2012
- Previous message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Next message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
Eric.
- Previous message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Next message: [Python-Dev] importlib is now bootstrapped (and what that means)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]