Eric Snow added the comment:
> 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".
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15502>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
