(original) (raw)



On Dec 9, 2017 8:53 PM, "INADA Naoki" <songofacandy@gmail.com> wrote:
> Earlier versions of PEP 538 thus included "en\_US.UTF-8" on the
\> candidate target locale list, but that turned out to cause assorted
\> problems due to the "C -> en\_US" part of the coercion.

Hm, but PEP 538 says:

\> 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.

https://www.python.org/dev/peps/pep-0538/#defaulting-to-surrogateescape-error-handling-on-the-standard-io-streams

I don't think en\_US.UTF-8 should use surrogateescape error handler.

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.

-Toshio