Message214426
| Author | pitrou |
|---|---|
| Recipients | benjamin.peterson, docs@python, eric.araujo, ezio.melotti, gwideman, lemburg, pitrou, tshepang, vstinner |
| Date | 2014-03-22.00:56:44 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1395449804.78.0.352952444937.issue20906@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> "UnicodeEncodeError: 'charmap' codec can't encode character '\u265e' in position 13: character maps to undefined". That's because stdout is treated as a regular bytestream under Windows (as it is under POSIX), and it therefore uses the current "codepage" to encode unicode strings. See issue1602. > And why does it work as intended on linux? Because under most current Linux systems, stdout's encoding will be utf-8, and therefore it will be able to represent the given unicode chars. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-22 00:56:45 | pitrou | set | recipients: + pitrou, lemburg, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, docs@python, tshepang, gwideman |
| 2014-03-22 00:56:44 | pitrou | set | messageid: <1395449804.78.0.352952444937.issue20906@psf.upfronthosting.co.za> |
| 2014-03-22 00:56:44 | pitrou | link | issue20906 messages |
| 2014-03-22 00:56:44 | pitrou | create | |