<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Dec 9, 2017 8:53 PM, "INADA Naoki" <<a href="mailto:songofacandy@gmail.com">songofacandy@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">> Earlier versions of PEP 538 thus included "en_US.UTF-8" on the<br>
> candidate target locale list, but that turned out to cause assorted<br>
> problems due to the "C -> en_US" part of the coercion.<br>
<br>
</div>Hm, but PEP 538 says:<br>
<br>
> this PEP instead proposes to extend the "surrogateescape" default for stdin and stderr error handling to also apply to the three potential coercion target locales.<br>
<br>
<a href="https://www.python.org/dev/peps/pep-0538/#defaulting-to-surrogateescape-error-handling-on-the-standard-io-streams" rel="noreferrer" target="_blank">https://www.python.org/dev/<wbr>peps/pep-0538/#defaulting-to-<wbr>surrogateescape-error-<wbr>handling-on-the-standard-io-<wbr>streams</a><br>
<br>
I don't think en_US.UTF-8 should use surrogateescape error handler.<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Could you explain why not? utf-8 seems like the common thread for using surrogateescape so I'm not sure what would make en_US.UTF-8 different than C.UTF-8.</div><div dir="auto"><br></div><div dir="auto">-Toshio</div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div></div></div></div>