Author ncoghlan
Recipients eric.araujo, martin.panter, ncoghlan, skrah, vstinner
Date 2014-05-03.04:29:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7fV2-yOji9Y7XVaUXSiDFDL1gHm-+1=SxmY5YbrqTHqxA@mail.gmail.com>
In-reply-to <1399057862.26.0.351789499422.issue21368@psf.upfronthosting.co.za>
Content
That's the problem - even on UTF-8 systems, Linux programs will often be
started in a misconfigured environment: the POSIX locale. Python 2 doesn't
try to interpret the binary data as text, so it doesn't care. Python 3
*does* care, since it automatically converts several pieces of OS provided
data to text using the locale encoding.

systemd tackles that by adding the extra config file to ensure *all* the
environments it creates get the right config, and to provide a more
reliable "source of truth" as to the actual likely encoding of system
interfaces.

However, a fair bit of groundwork is needed to avoid any innate reliance on
the locale encoding before we can reliably override it by default, so this
issue is unlikely to go anywhere before PEP 432 is implemented (and even
then, actually changing the behaviour would be a separate discussion).
History
Date User Action Args
2014-05-03 04:29:15ncoghlansetrecipients: + ncoghlan, vstinner, eric.araujo, skrah, martin.panter
2014-05-03 04:29:15ncoghlanlinkissue21368 messages
2014-05-03 04:29:13ncoghlancreate