[issue14846] Change in error when sys.path contains a nonexistent folder (importlib)

Roundup Robot added the comment: New changeset bfd04bfb55c5 by Nick Coghlan in branch 'default': Close #14846: Handle a sys.path entry going away http://hg.python.org/cpython/rev/bfd04bfb55c5 -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected status: open -> closed

[issue14846] Change in error when sys.path contains a nonexistent folder (importlib)

Changes by Eric V. Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue14846] Change in error when sys.path contains a nonexistent folder (importlib)

Eric Snow added the comment: The caching mechanism is going to check for changes in the directory. So the recommendation is to clear the cache manually: The default finders used by import now utilize a cache of what is contained within a specific directory. If you create a Python source

[issue14846] Change in error when sys.path contains a nonexistent folder (importlib)

Eric Snow added the comment: ...rather, the error caused by your example. :) -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue14846] Change in error when sys.path contains a nonexistent folder (importlib)

New submission from Thomas Kluyver : I've come across a difference from 3.2 to 3.3 while running the IPython test suite. It occurs when a directory on sys.path has been used for an import, then deleted without being removed from sys.path. Previous versions of Python ignore the nonexistent fold