imp.NullImporter should not be claiming that it is still used to fill sys.path_importer_cache on misses.

This seems like an oversight from

http://bugs.python.org/issue15473

The release notes for 3.3 added a note about this:
"Because None is now inserted into sys.path_importer_cache, if you are clearing out entries in the dictionary of paths that do not have a finder, you will need to remove keys paired with values of None and imp.NullImporter to be backwards-compatible. This will lead to extra overhead on older versions of Python that re-insert None into sys.path_importer_cache where it repesents the use of implicit finders, but semantically it should not change anything."

But the relevant docs for NullImporter (http://docs.python.org/2/library/imp.html#imp.NullImporter) and sys.path_importer_cache (http://docs.python.org/2/library/sys.html#sys.path_importer_cache) did not get updated.

We have verified that the release notes in 3.4 is correct, and NullImporter is never used.

We are however not sure about the correct wording for the documentation fix.

The docs for NullImporter need to not mention that it is used with sys.path_importer_cache since it isn't. As for sys.path_importer_cache, it should say that None is inserted and not NullImporter. Both need a versionchanged notation of the switch from None to NullImporter, but sys.path_importer_cache needs a special mention that to be fully backwards-compatible to check for both None and NullImporter.

And just to make sure you are looking at the right docs, Andreas, your links were to the Python 2.7 docs. If you look at the top of the docs you will see a dropdown which lets you switch to the 3.3 or 3.4 docs easily.

New changeset 8e390e4784b0 by Brett Cannon in branch 'default':
Issue #17176: Document that imp.NullImporter is no longer inserted
http://hg.python.org/cpython/rev/8e390e4784b0

New changeset e470370b4701 by Brett Cannon in branch '3.3':
Issue #17176: Document that imp.NullImporter is no longer
http://hg.python.org/cpython/rev/e470370b4701