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 martin.panter
Recipients Oren Milman, berker.peksag, brett.cannon, martin.panter
Date 2016-06-25.12:26:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466857580.82.0.941426270212.issue26896@psf.upfronthosting.co.za>
In-reply-to
Content
Oren: If you have extra changes to make on the same topic, it is probably best to make a new patch that combines both the original changes plus the new changes.

Brett: Since you were responsible for the two dead assignments, your input would be helpful. Perhaps you meant to add extra code and forgot, or perhaps they are just useless and we can remove them.

I skimmed over PEP 302, and it seems it uses the term “importer” more or less to mean what the current glossary terms “finder”. I.e. the first object to help with importing a module. Or maybe it means the system behind both the finder and loader stages, even if one object does not perform both steps. I don’t know much about this, but another option could be to redefine “importer” as it is more generally used.
History
Date User Action Args
2016-06-25 12:26:20martin.pantersetrecipients: + martin.panter, brett.cannon, berker.peksag, Oren Milman
2016-06-25 12:26:20martin.pantersetmessageid: <1466857580.82.0.941426270212.issue26896@psf.upfronthosting.co.za>
2016-06-25 12:26:20martin.panterlinkissue26896 messages
2016-06-25 12:26:20martin.pantercreate