Message270471
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). |
|
Date |
User |
Action |
Args |
2016-07-15 08:26:11 | ncoghlan | set | recipients:
+ ncoghlan, brett.cannon, eric.snow, martin.panter, wolma |
2016-07-15 08:26:11 | ncoghlan | set | messageid: <1468571171.43.0.324040534799.issue27487@psf.upfronthosting.co.za> |
2016-07-15 08:26:11 | ncoghlan | link | issue27487 messages |
2016-07-15 08:26:11 | ncoghlan | create | |
|