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 gvanrossum
Recipients Arfrever, asvetlov, barry, brett.cannon, chris.jerdonek, cvrebert, eric.snow, ezio.melotti, gvanrossum, pitrou, python-dev, serhiy.storchaka
Date 2013-07-01.17:43:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ok, the history of all that makes sense, except now I wonder if ModuleNotFoundError is useful at all.  I just reviewed a patch for 3.4 and in the latest revision all ImportError checks were replaced with ModuleNotFoundError checks.  What purpose does that have except encouraging code churn?
Date User Action Args
2013-07-01 17:43:18gvanrossumsetrecipients: + gvanrossum, barry, brett.cannon, pitrou, ezio.melotti, Arfrever, cvrebert, asvetlov, chris.jerdonek, python-dev, eric.snow, serhiy.storchaka
2013-07-01 17:43:18gvanrossumsetmessageid: <>
2013-07-01 17:43:18gvanrossumlinkissue15767 messages
2013-07-01 17:43:18gvanrossumcreate