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, python-dev
Date 2012-08-02.13:15:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343913334.25.0.0972202731645.issue15502@psf.upfronthosting.co.za>
In-reply-to
Content
OK, that last commit (along with one I did earlier for the import statement) brought over all the fixes I was previously overly hasty in committing to Barry's importdocs branch.

I've decided I can live with "regular packages" as the term for initialised packages (especially given the drawn out arguments on import-sig with the namespace package PEPs). If it becomes an anachronism by the time 4.0 rolls around, well, so be it.

The last big issue to be resolved is the terminology conflict between importlib.PathFinder, "path importer" and "importer. I think the first thing to try there is a rename to "importlib.PathImportFinder" and "path import finder" to see how well it reads.

My current feeling is that the result will have to be pretty horrible to make changing the long standing definition of "importer" to look like a superior option :)

I'm busy for the next couple of days though, so this may not make beta2
History
Date User Action Args
2012-08-02 13:15:34ncoghlansetrecipients: + ncoghlan, barry, brett.cannon, georg.brandl, eric.smith, Arfrever, python-dev, eric.snow
2012-08-02 13:15:34ncoghlansetmessageid: <1343913334.25.0.0972202731645.issue15502@psf.upfronthosting.co.za>
2012-08-02 13:15:33ncoghlanlinkissue15502 messages
2012-08-02 13:15:32ncoghlancreate