Author ncoghlan
Recipients brett.cannon, eric.snow, martin.panter, ncoghlan, wolma
Date 2016-07-15.08:26:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468571171.43.0.324040534799.issue27487@psf.upfronthosting.co.za>
In-reply-to
Content
No changes to 2.7 - the import system logic there is fairly different, since it's still using the old pre-importlib implementation.

For the "package.__main__" case, you're right that we don't want to emit the warning for "-m package", but we *do* want to emit the warning if package.__init__ imports package.__main__ for some reason.

And that's an excellent point about "finding spec" being implementer focused jargon - would "finding module specification" be clearer?

I'd still like to have a link between the error message and the fact the function is called "find_spec", and the official expansion of the abbreviation is "module specification" (hence _ModuleSpec).
History
Date User Action Args
2016-07-15 08:26:11ncoghlansetrecipients: + ncoghlan, brett.cannon, eric.snow, martin.panter, wolma
2016-07-15 08:26:11ncoghlansetmessageid: <1468571171.43.0.324040534799.issue27487@psf.upfronthosting.co.za>
2016-07-15 08:26:11ncoghlanlinkissue27487 messages
2016-07-15 08:26:11ncoghlancreate