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, barry, brett.cannon, eric.smith, eric.snow, georg.brandl, ncoghlan
Date 2012-08-01.05:13:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343798033.33.0.25581928155.issue15502@psf.upfronthosting.co.za>
In-reply-to
Content
> With the draft docs now comitted, this issue is the home for thrashing
> out the terminology.

In my mind the key is consistency.  While a worthy goal regardless, for the import system and its attendant complexity, consistency is crucial.

("importer" == finder + loader) sounds fine with me.  Even if some of these terms have been ambiguous in the past, I think that a consistent usage in the current docs will leave the ambiguity in the past.  I will advocate Barry's recommendation that we put a warning in PEP 302 that the terms there may be outdated.

I'm find with changing "path importer" to "path finder".  If no one does a patch first, I'll put one up tomorrow.

I actually prefer "path entry handler" for the distinctiveness, but I'm fine with leaving it be.  However, I get a sense that this is our one shot at this decision.

I'm also okay with renaming FileFinder to DirectoryHandler, particularly since it is a new class to 3.3 (no backward-compatibility issues).  Naturally this would parallel any decision on "path entry handler".
History
Date User Action Args
2012-08-01 05:13:53eric.snowsetrecipients: + eric.snow, barry, brett.cannon, georg.brandl, ncoghlan, eric.smith, Arfrever
2012-08-01 05:13:53eric.snowsetmessageid: <1343798033.33.0.25581928155.issue15502@psf.upfronthosting.co.za>
2012-08-01 05:13:52eric.snowlinkissue15502 messages
2012-08-01 05:13:50eric.snowcreate