Message257736
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? |
|
Date |
User |
Action |
Args |
2016-01-08 03:16:10 | martin.panter | set | recipients:
+ martin.panter, gvanrossum, vstinner, ezio.melotti, Emil Stenström |
2016-01-08 03:16:10 | martin.panter | set | messageid: <1452222970.74.0.537500483634.issue26045@psf.upfronthosting.co.za> |
2016-01-08 03:16:10 | martin.panter | link | issue26045 messages |
2016-01-08 03:16:10 | martin.panter | create | |
|