➜

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 eric.snow
Recipients Arfrever, asvetlov, barry, brett.cannon, chris.jerdonek, cvrebert, eric.snow, ezio.melotti, pitrou, serhiy.storchaka
Date 2013-02-20.03:50:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361332235.14.0.811034069491.issue15767@psf.upfronthosting.co.za>
In-reply-to
Content 
Right.  Sorry I wasn't more clear.  Existing code will continue to work either way.  The point is in exposing the distinct module/name-not-found case, which I consider to be the common case for catching ImportError.  My examples cover the case where you want to handle the module-not-found case specifically.
History
Date User Action Args
2013-02-20 03:50:35eric.snowsetrecipients: + eric.snow, barry, brett.cannon, pitrou, ezio.melotti, Arfrever, cvrebert, asvetlov, chris.jerdonek, serhiy.storchaka
2013-02-20 03:50:35eric.snowsetmessageid: <1361332235.14.0.811034069491.issue15767@psf.upfronthosting.co.za>
2013-02-20 03:50:35eric.snowlinkissue15767 messages
2013-02-20 03:50:34eric.snowcreate