Message195929
| Author | vstinner |
|---|---|
| Recipients | Arfrever, a.badger, abadger1999, benjamin.peterson, ezio.melotti, lemburg, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, vstinner |
| Date | 2013-08-22.22:11:49 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1377209509.92.0.695833940274.issue18713@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
>>> ('\udcff' + 'qwerty').encode('utf-16le', 'surrogateescape')
b'\xff\xdcq\x00w\x00e\x00r\x00t\x00y\x00'
Oh, this is a bug in the UTF-16 encoder: it should not encode surrogate characters => see issue #12892
I read that it's possible to set a standard stream like stdout in UTF-16 mode on Windows. I don't know if it's commonly used, nor it would impact Python. I never see a platform using UTF-16 or UTF-32 for standard streams. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-22 22:11:49 | vstinner | set | recipients: + vstinner, lemburg, ncoghlan, pitrou, abadger1999, benjamin.peterson, ezio.melotti, a.badger, Arfrever, r.david.murray, serhiy.storchaka |
| 2013-08-22 22:11:49 | vstinner | set | messageid: <1377209509.92.0.695833940274.issue18713@psf.upfronthosting.co.za> |
| 2013-08-22 22:11:49 | vstinner | link | issue18713 messages |
| 2013-08-22 22:11:49 | vstinner | create | |