Message205673
| Author |
lemburg |
| Recipients |
a.badger, bkabrda, deleted250130, larry, lemburg, loewis, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, terry.reedy, vstinner |
| Date |
2013年12月09日.10:30:11 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<52A59BB1.40007@egenix.com> |
| In-reply-to |
<1386584350.77.0.371148951076.issue19846@psf.upfronthosting.co.za> |
| Content |
On 09.12.2013 11:19, STINNER Victor wrote:
>
> STINNER Victor added the comment:
>
> Marc-Andre> AFAIK, Python 3 does work with ASCII data in the C locale, so I'm not sure whether this is a bug at all.
>
> What do you mean? Python uses the surrogateescape encoding since Python 3.1, undecodable bytes are stored as surrogate characters.
>
> Many bugs related to locales were fixed in Python 3.2, 3.3 and 3.4.
>
> There are remaining bugs?
I was referring to the original bug report on this ticket.
FWIW: I don't think you can expect Python to work without exceptions
if you use a C locale and write non-ASCII data to stdout. I also
don't think that the new ticket title is correct - or at least,
I fail to see which aspect of Python breaks with LANG=C :-) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年12月09日 10:30:12 | lemburg | set | recipients:
+ lemburg, loewis, terry.reedy, ncoghlan, pitrou, vstinner, larry, a.badger, r.david.murray, deleted250130, serhiy.storchaka, bkabrda |
| 2013年12月09日 10:30:12 | lemburg | link | issue19846 messages |
| 2013年12月09日 10:30:11 | lemburg | create |
|