Message160058
The piece you're missing is that the interpreter state holds a direct reference to the import machinery in interp->importlib, and *that's* what gets used by the builtin __import__ implementation.
I'm beginning to think the thing to do is to simply say "yes, there are two copies of importlib._bootstrap". By default, the compiled in one is used, but you can replace it with the on-disk one by appropriately editing sys.meta_path and sys.path_hooks.
Trying to hide it isn't going to eliminate the potential problems - it's just going to move the problems around (and likely make them even more confusing in the process). |
|
Date |
User |
Action |
Args |
2012-05-06 07:04:57 | ncoghlan | set | recipients:
+ ncoghlan, lemburg, brett.cannon, pitrou, eric.smith, eric.araujo, Arfrever, python-dev, eric.snow |
2012-05-06 07:04:57 | ncoghlan | set | messageid: <1336287897.81.0.0688531045234.issue14657@psf.upfronthosting.co.za> |
2012-05-06 07:04:56 | ncoghlan | link | issue14657 messages |
2012-05-06 07:04:56 | ncoghlan | create | |
|