On Mon, Apr 16, 2012 at 2:31 AM, Brett Cannon <brett@python.org> wrote:
> What about sys.path_importer_cache: all of it or just NullImporter/None
> entries (or should that be a boolean to this function)? And shouldn't it be
> called reset_import() with the level of changes you are proposing the
> function make?

Hmm, perhaps the simpler suggestion is: "If you want a clean import
state, use multiprocessing or the subprocess module to invoke a new
instance of python" :)


Yeah, kinda. =) This is why testing import (as you know) is such an utter pain.

-Brett

 
">

(original) (raw)



On Sun, Apr 15, 2012 at 22:03, Nick Coghlan <ncoghlan@gmail.com> wrote:

On Mon, Apr 16, 2012 at 2:31 AM, Brett Cannon <brett@python.org> wrote:
> What about sys.path\_importer\_cache: all of it or just NullImporter/None
> entries (or should that be a boolean to this function)? And shouldn't it be
> called reset\_import() with the level of changes you are proposing the
> function make?

Hmm, perhaps the simpler suggestion is: "If you want a clean import
state, use multiprocessing or the subprocess module to invoke a new
instance of python" :)


Yeah, kinda. =) This is why testing import (as you know) is such an utter pain.

-Brett

Cheers,
Nick.

\--
Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia