Message195862
| Author | vstinner |
|---|---|
| Recipients | Arfrever, a.badger, abadger1999, benjamin.peterson, ezio.melotti, lemburg, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, vstinner |
| Date | 2013-08-22.06:53:28 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAMpsgwY+YuNiRRJtKAMZnEH1oaUY73E+CGv6RbzngixUPft05g@mail.gmail.com> |
| In-reply-to | <1377150467.74.0.78539952282.issue18713@psf.upfronthosting.co.za> |
| Content | |
|---|---|
"The surrogateescape error handler works with any codec." The surrogatepass only works with utf-8 if I remember correctly. The surrogateescape error handler works with any codec, especially ascii. "As a side effect of this change an input from stdin will be incompatible in general with extensions which implicitly encode a string to bytes with UTF-8 (e.g. tkinter, XML parsers, sqlite3, datetime, locale, curses, etc.)" Correct, but it's not something new: os.listdir(), sys.argv, os.environ and other functions using os.fsdecode(). Applications should already have to support surrogates. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-22 06:53:28 | vstinner | set | recipients: + vstinner, lemburg, ncoghlan, pitrou, abadger1999, benjamin.peterson, ezio.melotti, a.badger, Arfrever, r.david.murray, serhiy.storchaka |
| 2013-08-22 06:53:28 | vstinner | link | issue18713 messages |
| 2013-08-22 06:53:28 | vstinner | create | |