This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Sworddragon, a.badger, bkabrda, ezio.melotti, ishimoto, jwilk, larry, loewis, martin.panter, ncoghlan, pitrou, python-dev, r.david.murray, serhiy.storchaka, vstinner
Date 2014-04-28.17:13:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398705195.2393.5.camel@fsol>
In-reply-to <>
> The conclusion I have come to is that any further decoupling of Python 3
> from the locale encoding will actually depend on getting the PEP 432
> bootstrapping changes implemented, reviewed and the PEP approved, so we
> have more interpreter infrastructure in place by the time the interpreter
> starts trying to figure out all these boundary encoding issues.

Yeah. My proposal had more to do with the fact that we should some day
switch to utf-8 by default on all POSIX systems, regardless of what the
system advertises as "best encoding".
Date User Action Args
2014-04-28 17:13:17pitrousetrecipients: + pitrou, loewis, ishimoto, ncoghlan, vstinner, larry, jwilk, ezio.melotti, a.badger, r.david.murray, Sworddragon, python-dev, martin.panter, serhiy.storchaka, bkabrda
2014-04-28 17:13:17pitroulinkissue19977 messages
2014-04-28 17:13:17pitroucreate