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 Arfrever, barry, brett.cannon, eric.smith, eric.snow, georg.brandl, ncoghlan
Date 2012-08-01.22:17:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120801181747.7e9a6275@resist.wooz.org>
In-reply-to <CADiSq7cDEyPAQrmCM0SYeZeb_HZfuTjhsZSKd=e89zJ0gifhbQ@mail.gmail.com>
Content
On Aug 01, 2012, at 10:03 PM, Nick Coghlan wrote:

>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"

-0.  To me, this doesn't make things vastly more clear for the additional
awkwardness in readability.

>"path_importer_cache" would still be a bit of a misnomer, but that ship
>sailed a long time ago.

Yeah, we all agree that one's unfortunate! ;)
History
Date User Action Args
2012-08-01 22:17:56barrysetrecipients: + barry, brett.cannon, georg.brandl, ncoghlan, eric.smith, Arfrever, eric.snow
2012-08-01 22:17:55barrylinkissue15502 messages
2012-08-01 22:17:53barrycreate