RetroSearch Browse

Wed Mar 15 10:30:08 EDT 2017 · https://mail.python.org/pipermail/python-dev/2017-March/147614.html

On Mar 15, 2017, at 12:29 PM, Nick Coghlan wrote:

>From a mainstream Linux point of view, it's not common - on systemd-managed
>systems, for example, the only way to get the C locale these days is to
>either specify it in /etc/locale.conf, or to set it specifically in the
>environment.

I think it's still the case that some isolation environments (e.g. Debian
chroots) default to bare C locales.  Often it doesn't matter, but sometimes
tests or other applications run inside those environments will fail in ways
they don't in a normal execution environment.  The answer is almost always to
explicitly coerce those environments to C.UTF-8 for Linuxes that support that.

-Barry

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2017-March/147614.html below:

[Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale