Message182271
| Author |
brett.cannon |
| Recipients |
asvetlov, barry, brett.cannon, chris.jerdonek, cvrebert, eric.snow, ezio.melotti, maker, serhiy.storchaka |
| Date |
2013年02月17日.14:43:55 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1361112235.88.0.0382764795675.issue15767@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Eric: knock yourself out. =)
Serhiy: What exception is raised in that situation is controlled by the eval loop, not importlib so that would be a separate change. But regardless, there is no way to infer whether you expected an attribute or module to be there, just that you were after something that didn't exist. But I would argue most people import at the module level and not the attribute level, and so raising an ModuleNotFoundError would be acceptable. |
|