Author pitrou
Recipients Arfrever, brett.cannon, eric.smith, eric.snow, ncoghlan, pitrou
Date 2012-04-24.09:06:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335258297.3436.8.camel@localhost.localdomain>
In-reply-to <1335242418.38.0.457809991662.issue14657@psf.upfronthosting.co.za>
Content
> This would also mean that changes to importlib._bootstrap would
> actually take effect for user code almost immediately, *without*
> rebuilding Python, as the frozen version would *only* be used to get
> hold of the pure Python version.

Actually, _io, encodings and friends must be loaded before importlib
gets imported from Python code, so you will still have __loader__
entries referencing the frozen importlib, unless you also rewrite these
attributes.

My desire here is not to hide _frozen_importlib, rather to avoid subtle
issues with two instances of a module living in memory with separate
global states. Whether it's the frozen version or the on-disk Python
version that gets the preference is another question (a less important
one in my mind).
History
Date User Action Args
2012-04-24 09:06:19pitrousetrecipients: + pitrou, brett.cannon, ncoghlan, eric.smith, Arfrever, eric.snow
2012-04-24 09:06:19pitroulinkissue14657 messages
2012-04-24 09:06:19pitroucreate