| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fromlist of __import__ propagate.
The problem previously was that if something listed in fromlist didn't
exist then that's okay. The fix for that was too broad in terms of
catching ImportError.
The trick with the solution to this issue is that the proper
refactoring of import thanks to importlib doesn't allow for a way to
distinguish (portably) between an ImportError because finders couldn't
find a loader, or a loader raised the exception. In Python 3.4 the
hope is to introduce a new exception (e.g. ModuleNotFound) to make it
clean to differentiate why ImportError was raised.
|
| | |
|
| |
|
|
|
| |
module again. Also took the opportunity to stop accidentally exporting
_imp.extension_suffixes() as public.
|
| |
|
|
|
|
|
|
|
| |
state of the import system. Also make importlib.invalidate_caches()
work with sys.meta_path instead of sys.path_importer_cache to
completely separate the path-based import system from the overall
import system.
Patch by Eric Snow.
|
| |
|
|
| |
the name into line with normal import terminology. Original patch by Eric Snow
|
| |
|
|
| |
the import protocols given PEP 420. Original patch by Eric Snow.
|
| | |
|
| | |
|
| |
|
|
|
| |
visible and to place it with other micro-benchmarks (e.g.
stringbench).
|
|
|
This should make the Linux distros happy as it is now easier to leave
importlib's tests out of their base Python distribution.
|