This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.snow
Recipients Arfrever, Marc.Abramowitz, Ronan.Lamy, brett.cannon, chris.jerdonek, eric.smith, eric.snow, pnasrat, python-dev
Date 2012-07-07.17:10:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341681054.2.0.880429176101.issue14982@psf.upfronthosting.co.za>
In-reply-to
Content
Importers are a PEP 302 API.  In the context of pkgutil, they are path hooks (see http://www.python.org/dev/peps/pep-0302/#id24), aka path importers.  A path hook is a callable that takes a path and returns a finder.  Path hooks are stored in sys.path_hooks and the finder resulting from a matching path importer is stored in sys.path_importer_cache.

pkgutil also refers to PEP 302 finders as "importers".  To be honest, the import-related nomenclature is a mess.

While you can use pkgutil.ImpImporter as a path hook, instances can also be used as metapath hooks; if you don't pass anything to ImpImporter, the resulting object acts more like a PEP 302 metapath hook that wraps the "default" import process.

(See Lib/pkgutil.py)
History
Date User Action Args
2012-07-07 17:10:54eric.snowsetrecipients: + eric.snow, brett.cannon, eric.smith, Arfrever, pnasrat, chris.jerdonek, python-dev, Marc.Abramowitz, Ronan.Lamy
2012-07-07 17:10:54eric.snowsetmessageid: <1341681054.2.0.880429176101.issue14982@psf.upfronthosting.co.za>
2012-07-07 17:10:53eric.snowlinkissue14982 messages
2012-07-07 17:10:53eric.snowcreate