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, pitrou, skrah
Date 2012-07-31.20:08:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120731160807.528d6873@limelight.wooz.org>
In-reply-to <1343704869.56.0.834482644373.issue15295@psf.upfronthosting.co.za>
Content
On Jul 31, 2012, at 03:21 AM, Eric Snow wrote:

>1. default path importer (a.k.a PathFinder),

+1, although currently I am refraining from using "default" when describing
this thing.

>2. path hook (lives on sys.path_hooks),

I have called these "path entry hooks"

>3. path entry handler (finder look-alike that a path hook returns),

I still call these "path entry finders".  I understand the ambiguity, and
despite supporting a slightly different protocol than meta path finders, they
still serve the role of finding a loader for a module.  So for now, I'm
keeping "path entry finder", though I'll leave the door slightly open to
persuasion. :)

>4. module loader (business as usual).

I've pulled "Loaders" out into a separate higher level section because as you
say, the loader API is the same for the things returned by both meta path
finders and path entry finders.
History
Date User Action Args
2012-07-31 20:08:11barrysetrecipients: + barry, brett.cannon, georg.brandl, ncoghlan, pitrou, larry, eric.araujo, skrah, eric.snow
2012-07-31 20:08:10barrylinkissue15295 messages
2012-07-31 20:08:08barrycreate