[issue15473] importlib no longer uses imp.NullImporter

2012-08-03 Thread Brett Cannon
Changes by Brett Cannon : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue15473] importlib no longer uses imp.NullImporter

2012-08-02 Thread Nick Coghlan
Nick Coghlan added the comment: Barry covered it in a footnote -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue15473] importlib no longer uses imp.NullImporter

2012-08-02 Thread Brett Cannon
Brett Cannon added the comment: Did this get addressed in the final doc update? -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15473] importlib no longer uses imp.NullImporter

2012-07-29 Thread Brett Cannon
Brett Cannon added the comment: On Jul 29, 2012 12:21 AM, "Nick Coghlan" wrote: > > > Nick Coghlan added the comment: > > See the porting notes: http://docs.python.org/dev/whatsnew/3.3.html#porting-python-code > > With the removal of the implicit default finder, the 3.3 semantics are that both N

[issue15473] importlib no longer uses imp.NullImporter

2012-07-28 Thread Nick Coghlan
Nick Coghlan added the comment: See the porting notes: http://docs.python.org/dev/whatsnew/3.3.html#porting-python-code With the removal of the implicit default finder, the 3.3 semantics are that both None *and* imp.NullImporter mean "There is no importer for this path". -- _

[issue15473] importlib no longer uses imp.NullImporter

2012-07-27 Thread Barry A. Warsaw
New submission from Barry A. Warsaw : I think this is mostly just out of date documentation, but I want to get Brett's feedback. The sys module has this to say about sys.path_importer_cache: "A dictionary acting as a cache for finder objects. The keys are paths that have been passed to sys.pa