This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients barry
Date 2012-11-20.15:17:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
When sys.path[0] is None, attempting to import a module produces a cryptic chained traceback.  This is a regression from 3.2 where the import would succeed.

The basic issue is that in 3.2's import.c, non-string/bytes items on sys.path are essentially ignored (see the loop in import.c:1708 find_module()) while they are not ignored in 3.3's importlib.  This means that because zipimporter.zipimiporter is by default the first thing on sys.path_hooks, zipimporter.zipimporter(None) gets called.  This raises a TypeError which starts the chained exception.  Note that the fact that zipimporter.zipimporter(None) raises a TypeError is *not* a regression.  The regression is that None makes its way to sys.path_hooks at all.

I think this will be relatively easy to fix, if we agree that the current regressive behavior is a bug.
Date User Action Args
2012-11-20 15:17:15barrysetrecipients: + barry
2012-11-20 15:17:15barrysetmessageid: <>
2012-11-20 15:17:15barrylinkissue16514 messages
2012-11-20 15:17:14barrycreate