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:44:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7eJLdYN9+s4hxf7QL6PNc-Ce-Ad9z3fc+cg34bKp1mK8w@mail.gmail.com>
In-reply-to <20120801181747.7e9a6275@resist.wooz.org>
Content
The problem with "path importer" is it's just plain *wrong*. That object is
not an importer and thus calling it one makes it much harder to learn the
finder/loader/importer distinctions correctly. "import finder" is only
slightly longer than "importer" and has the huge advantage of *not being
wrong*.
History
Date User Action Args
2012-08-01 22:44:54ncoghlansetrecipients: + ncoghlan, barry, brett.cannon, georg.brandl, eric.smith, Arfrever, eric.snow
2012-08-01 22:44:53ncoghlanlinkissue15502 messages
2012-08-01 22:44:52ncoghlancreate