Chris Jerdonek chris.jerdo...@gmail.com added the comment:
Closing as this is no longer an issue after Nick's pkgutil changes documented
in issue 15343.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15297
___
Ronan Lamy ronan.l...@gmail.com added the comment:
AFAICT, the intent of this function was to help provide a fully PEP-302
compliant import process wrapping the builtin C-implemented import mechanism.
Nowadays, I believe that iterating over sys.meta_path should probably be enough.
--
Chris Jerdonek chris.jerdo...@gmail.com added the comment:
Marking this a documentation issue because the same behavior is also present in
2.7:
Python 2.7.3 (default, Apr 19 2012, 00:55:09)
[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin
from pkgutil import
New submission from Chris Jerdonek chris.jerdo...@gmail.com:
I'm not sure if this should be fixed in the code or in the documentation, but
the pkgutil.iter_importers() documentation says that
pkgutil.iter_importers(name) should yield the importers for sys.meta_path,
sys.path, and Python’s
