➜

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 Arfrever, Guido.van.Rossum, asvetlov, barry, brett.cannon, chris.jerdonek, cvrebert, eric.snow, ezio.melotti, gvanrossum, pitrou, python-dev, serhiy.storchaka, theller
Date 2013-07-02.12:03:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20130702080257.7b817d57@limelight.wooz.org>
In-reply-to <1372749390.54.0.352874671477.issue15767@psf.upfronthosting.co.za>
Content 
On Jul 02, 2013, at 07:16 AM, Serhiy Storchaka wrote:

>If most user code should catch a ModuleNotFoundError exception, perhaps it
>will be better rename old ImportError to ImportlibError (or ImportingError,
>or ImportMachineryError, or BaseImportError) and new ModuleNotFoundError to
>ImportError. This will left most existing user code untouched.

I urge some caution here.  I don't know that the above will cause problems,
but I do think you're walking into PEP territory.  I would feel much more
comfortable with an analysis based on testing existing third party code.
History
Date User Action Args
2013-07-02 12:03:00barrysetrecipients: + barry, gvanrossum, brett.cannon, theller, pitrou, ezio.melotti, Arfrever, cvrebert, asvetlov, chris.jerdonek, python-dev, eric.snow, serhiy.storchaka, Guido.van.Rossum
2013-07-02 12:03:00barrylinkissue15767 messages
2013-07-02 12:03:00barrycreate