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 brett.cannon
Recipients Arfrever, asvetlov, barry, brett.cannon, chris.jerdonek, cvrebert, eric.snow, ezio.melotti, pitrou, serhiy.storchaka
Date 2013-02-19.19:49:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Chris: Having a more generic name for import-from at the eval loop level on top of NoModuleFoundError is breaking the "practicality over purity" rule. ImportSearchFailed might be the closest we can come to a generic name for what occurred.

Serihy & Barry: no. We do that now and it's already a nasty little hack. It would be better to let people catch an exception signaling that an import didn't happen because some module is missing than require introspection on a caught ImportError to tell what is going on (there's a reason why Antoine went to all of that trouble to add new exceptions so we don't have to look at the errno attribute on OSError). Exceptions are structured to work off of inheritance hierarchies (says the man who co-wrote the PEP to make all PEPs inherit from BaseException).
Date User Action Args
2013-02-19 19:49:38brett.cannonsetrecipients: + brett.cannon, barry, pitrou, ezio.melotti, Arfrever, cvrebert, asvetlov, chris.jerdonek, eric.snow, serhiy.storchaka
2013-02-19 19:49:38brett.cannonsetmessageid: <>
2013-02-19 19:49:38brett.cannonlinkissue15767 messages
2013-02-19 19:49:37brett.cannoncreate