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 pitrou
Recipients Arfrever, amaury.forgeotdarc, brett.cannon, georg.brandl, gvanrossum, pitrou, r.david.murray
Date 2012-06-25.20:40:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340656827.55.0.956506343754.issue15110@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, you're right. But it could become confusing if some error is raised inside of importlib itself (not an ImportError, something else - perhaps a bug).

So I would suggest the following:
- trim ImportErrors
- trim errors raised when executing the code of an imported module (i.e. in _LoaderBasics._load_module())
- don't trim other errors, since they can be importlib programming errors
History
Date User Action Args
2012-06-25 20:40:27pitrousetrecipients: + pitrou, gvanrossum, brett.cannon, georg.brandl, amaury.forgeotdarc, Arfrever, r.david.murray
2012-06-25 20:40:27pitrousetmessageid: <1340656827.55.0.956506343754.issue15110@psf.upfronthosting.co.za>
2012-06-25 20:40:26pitroulinkissue15110 messages
2012-06-25 20:40:26pitroucreate