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 ncoghlan
Recipients Arfrever, barry, brett.cannon, eric.smith, eric.snow, georg.brandl, ncoghlan
Date 2012-08-01.22:03:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7cDEyPAQrmCM0SYeZeb_HZfuTjhsZSKd=e89zJ0gifhbQ@mail.gmail.com>
In-reply-to <1343841587.67.0.871056672327.issue15502@psf.upfronthosting.co.za>
Content
As a final attempt at giving the path import machinery the emphasis it
deserves without misusing the "importer" term, how about:
1. "path import subsystem" for that whole section of the import machinery;
and
2. "path import finder" specifically for the meta path finder that
importlib calls "PathFinder" and the new docs currently call "path importer"

"path_importer_cache" would still be a bit of a misnomer, but that ship
sailed a long time ago.
History
Date User Action Args
2012-08-01 22:03:29ncoghlansetrecipients: + ncoghlan, barry, brett.cannon, georg.brandl, eric.smith, Arfrever, eric.snow
2012-08-01 22:03:28ncoghlanlinkissue15502 messages
2012-08-01 22:03:28ncoghlancreate