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
test___loader__.py	Normalize whitespace	2013-03-13 10:45:33 -07:00
test___package__.py
test_api.py	Issue #15767: Introduce ModuleNotFoundError, a subclass of	2013-06-12 16:59:46 -04:00
test_caching.py
test_fromlist.py	Issue #15767: Introduce ModuleNotFoundError, a subclass of	2013-06-12 16:59:46 -04:00
test_meta_path.py
test_packages.py
test_path.py	Do a better job of preserving the state of sys.modules.	2012-11-20 17:10:10 -05:00
test_relative_imports.py
util.py