On Dec 9, 2017 8:53 PM, "INADA Naoki" <songofaca...@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
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
