New submission from Wolfgang Richter: My understanding of `sys.meta_path` is that it is supposed to allow customized loading of Python modules and packages.
In fact the `importlib` machinery appears to have support for identifying packages with `__init__` files with non-standard suffixes: https://github.com/python/cpython/blob/master/Lib/importlib/_bootstrap_external.py#L645 https://github.com/python/cpython/blob/master/Lib/importlib/_bootstrap_external.py#L1233 However, I find that when I `import wolftest` inside a folder with structure: ./ /wolftest /__init__.wolf /something.wolf None of my sys.meta_path finders are called at all, and instead a namespace is returned. I was wondering why the `import` statement appears to short-circuit and not check with `sys.meta_path` handlers in this case? ---------- components: Library (Lib) files: PyMetaPath.tar.gz messages: 260138 nosy: Wolfgang Richter priority: normal severity: normal status: open title: `sys.meta_path` Skipped for Packages with Non-Standard Suffixed `__init__` Files type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file41902/PyMetaPath.tar.gz _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26344> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
