Barry A. Warsaw added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15767> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
