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 steve.dower
Recipients eric.snow, lemburg, python-dev, steve.dower, syeberman
Date 2016-09-08.13:18:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473340700.8.0.405227208648.issue28005@psf.upfronthosting.co.za>
In-reply-to
Content
Is it deliberate that inner import errors should be treated as if the codec is missing? Another search function isn't going to help in that case unless it finds the same encoding in another place. I didn't see any evidence of that, and apparently neither did Eric (but I was bitten by a misspelt import within my new encodings/oem.py giving a confusing message).

I don't think any encoding modules in the stdlib should fail to import. This change ensures that we hear about it if they do fail.
History
Date User Action Args
2016-09-08 13:18:20steve.dowersetrecipients: + steve.dower, lemburg, syeberman, python-dev, eric.snow
2016-09-08 13:18:20steve.dowersetmessageid: <1473340700.8.0.405227208648.issue28005@psf.upfronthosting.co.za>
2016-09-08 13:18:20steve.dowerlinkissue28005 messages
2016-09-08 13:18:20steve.dowercreate