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 barry
Recipients barry, brett.cannon, eric.araujo, eric.snow, georg.brandl, larry, ncoghlan, skrah
Date 2012-07-31.19:52:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120731155251.0dcf0ede@limelight.wooz.org>
In-reply-to <1343694484.08.0.513510031013.issue15295@psf.upfronthosting.co.za>
Content
I think I was unclear in my previous follow up.  Here are the objects
involved, taken from the glossary.

   import path
      A list of locations (or :term:`path entries <path entry>`) that are
      searched by the :term:`path importer` for modules to import.  During
      import, this list of locations usually comes from :data:`sys.path`, but
      for subpackages it may also come from the parent package's ``__path__``
      attribute.

   meta path finder
      A finder returned by a search of :data:`sys.meta_path`.  Meta path
      finders are related to, but different from :term:`path entry finders
      <path entry finder>`.

   path entry
      A single location on the :term:`import path` which the :term:`path
      importer` consults to find modules for importing.

   path entry finder
      A :term:`finder` returned by a callable on :data:`sys.path_hooks`
      (i.e. a :term:`path entry hook`) which knows how to locate modules given
      a :term:`path entry`.

   path entry hook
      A callable on the :data:`sys.path_hook` list which returns a :term:`path
      entry finder` if it knows how to find modules on a specific :term:`path
      entry`.

   path importer
      One of the default :term:`meta path finders <meta path finder>` which
      searches an :term:`import path` for modules.
History
Date User Action Args
2012-07-31 19:52:53barrysetrecipients: + barry, brett.cannon, georg.brandl, ncoghlan, larry, eric.araujo, skrah, eric.snow
2012-07-31 19:52:52barrylinkissue15295 messages
2012-07-31 19:52:51barrycreate