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 r.david.murray
Recipients ezio.melotti, r.david.murray, techtonik
Date 2013-03-16.16:03:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1363449792.22.0.0906072798566.issue17439@psf.upfronthosting.co.za>
In-reply-to
Content
Python doesn't store the encoding information anywhere.  The coding cookie is used to correctly convert the bytes in the file into unicode...otherwise they are just treated as bytes.

For the stdin case, the encoding is associated with the input stream, and again you either get unicode or bytes, there is no encoding information that is carried along with the data.

So, when the conversion is attempted, there is no encoding information available to add to the error message.
History
Date User Action Args
2013-03-16 16:03:12r.david.murraysetrecipients: + r.david.murray, techtonik, ezio.melotti
2013-03-16 16:03:12r.david.murraysetmessageid: <1363449792.22.0.0906072798566.issue17439@psf.upfronthosting.co.za>
2013-03-16 16:03:12r.david.murraylinkissue17439 messages
2013-03-16 16:03:12r.david.murraycreate