Message195931
| Author |
ncoghlan |
| Recipients |
Arfrever, a.badger, abadger1999, benjamin.peterson, ezio.melotti, lemburg, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, vstinner |
| Date |
2013年08月22日.23:04:42 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CADiSq7chcoDYZD+vBZqxa7Dv_8crqmo4y6OCTaAK7tuTuwV9Gg@mail.gmail.com> |
| In-reply-to |
<1377186038.8.0.16299145899.issue18713@psf.upfronthosting.co.za> |
| Content |
On 23 Aug 2013 01:40, "R. David Murray" <report@bugs.python.org> wrote:
. (I double checked, and this does indeed work...doing the equivalent of
ls >temp via python preserves the bytes with that PYTHONIOENCODING setting.
I don't quite understand, however, why I get the � chars if I don't
redirect the output.).
I assume the terminal window is doing the substitution for the improperly
encoded bytes.
Regarding the issue, perhaps we should convert this to a docs bug? Attempt
to make the "PYTHONIOENCODING=utf-8:surrogateescape" easier to discover?
Heck, it may be worth creating a stable URL that we can include in
surrogate related error messages... |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年08月22日 23:04:42 | ncoghlan | set | recipients:
+ ncoghlan, lemburg, pitrou, vstinner, abadger1999, benjamin.peterson, ezio.melotti, a.badger, Arfrever, r.david.murray, serhiy.storchaka |
| 2013年08月22日 23:04:42 | ncoghlan | link | issue18713 messages |
| 2013年08月22日 23:04:42 | ncoghlan | create |
|