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 ncoghlan
Recipients brett.cannon, davin, dw, eric.snow, ncoghlan
Date 2018-12-19.13:52:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545227569.28.0.788709270274.issue35486@psf.upfronthosting.co.za>
In-reply-to
Content
The two errors mean different things: ModuleNotFoundError means literally that the module could not be found at all (i.e. no import hook offered to try to load it)

A plain ImportError then means that the module was located, but attempting to actually load it failed.

find_spec()/find_loader()/find_module() implementations on import plugins shouldn't be raising exceptions for modules they don't offer, and hence shouldn't be needing to raise ModuleNotFoundError directly.
History
Date User Action Args
2018-12-19 13:52:49ncoghlansetrecipients: + ncoghlan, brett.cannon, eric.snow, dw, davin
2018-12-19 13:52:49ncoghlansetmessageid: <1545227569.28.0.788709270274.issue35486@psf.upfronthosting.co.za>
2018-12-19 13:52:49ncoghlanlinkissue35486 messages
2018-12-19 13:52:49ncoghlancreate