Message257736
| Author |
martin.panter |
| Recipients |
Emil Stenström, ezio.melotti, gvanrossum, martin.panter, vstinner |
| Date |
2016-01-08.03:16:10 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1452222970.74.0.537500483634.issue26045@psf.upfronthosting.co.za> |
| In-reply-to |
|
| Content |
After reading through the linked thread, there are a few error message proposals:
Guido: "use data.encode('utf-8') if you want the data to be encoded in UTF-8". (Then of course the server might not like it.)
Andrew Barnert: A UnicodeEncodeError (or subclass of it?) with text like "HTTP body without encoding defaults to 'latin-1', which can't encode character '\u5555' in position 30: ordinal not in range(256)")
Paul Moore: Encode as ASCII and catch UnicodeEncodeError and re-raise as a TypeError "Unicode string supplied without an explicit encoding".
Emil, do you think any of these would help? |
|