[Python-Dev] making the import machinery explicit (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon Apr 16 04:03:05 CEST 2012
- Previous message: [Python-Dev] making the import machinery explicit
- Next message: [Python-Dev] making the import machinery explicit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Apr 16, 2012 at 2:31 AM, Brett Cannon <brett at python.org> wrote:
What about sys.pathimportercache: all of it or just NullImporter/None entries (or should that be a boolean to this function)? And shouldn't it be called resetimport() 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" :)
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] making the import machinery explicit
- Next message: [Python-Dev] making the import machinery explicit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]