cpython/Lib/importlib
Brett Cannon b1611e2772 Issue #15767: Introduce ModuleNotFoundError, a subclass of
ImportError.

The exception is raised by import when a module could not be found.
Technically this is defined as no viable loader could be found for the
specified module. This includes ``from ... import`` statements so that
the module usage is consistent for all situations where import
couldn't find what was requested.

This should allow for the common idiom of::

  try:
    import something
  except ImportError:
    pass

to be updated to using ModuleNotFoundError and not accidentally mask
ImportError messages that should propagate (e.g. issues with a
loader).

This work was driven by the fact that the ``from ... import``
statement needed to be able to tell the difference between an
ImportError that simply couldn't find a module (and thus silence the
exception so that ceval can raise it) and an ImportError that
represented an actual problem.
2013-06-12 16:59:46 -04:00
..
__init__.py Issue #17099: Have importlib.find_loader() raise ValueError when 2013-03-13 11:09:08 -07:00
_bootstrap.py Issue #15767: Introduce ModuleNotFoundError, a subclass of 2013-06-12 16:59:46 -04:00
abc.py Issues #18088, 18089: Introduce 2013-05-31 18:56:47 -04:00
machinery.py Issue #15576: Allow extension modules to be a package's __init__ 2012-08-10 13:47:54 -04:00
util.py fix whitespace 2013-05-31 18:57:45 -04:00