Author pitrou
Recipients Arfrever, brett.cannon, eric.smith, eric.snow, ncoghlan, pitrou
Date 2012-04-24.08:10:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335254938.3436.3.camel@localhost.localdomain>
In-reply-to <1335228102.81.0.191480459618.issue14657@psf.upfronthosting.co.za>
Content
> So why the mutation? Are you that worried someone is going to import
> importlib._bootstrap directly?

Well, importing importlib *does* import importlib._bootstrap, and
creates another copy of the module. importlib.__import__ is then wired
to _bootstrap.__import__, which is different from the built-in
__import__ (potentially using different globals, for example).

> This also costs in development complexity because not only do you have
> to run 'make' to get changes to be testable, but it also leads to
> difficult debugging situations where if you are not totally sure you
> got something working you won't find out until you see e.g. that the
> standard I/O streams were not initialized.

I'm worried that two different copies of importlib will lead to its own
difficult debugging situations.
History
Date User Action Args
2012-04-24 08:10:20pitrousetrecipients: + pitrou, brett.cannon, ncoghlan, eric.smith, Arfrever, eric.snow
2012-04-24 08:10:20pitroulinkissue14657 messages
2012-04-24 08:10:20pitroucreate