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 ncoghlan
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:11:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <1398679645.2302.1.camel@fsol>
Victor was referring to code like "print(os.listdir())". Those are the
motivating cases for ensuring round trips from system APIs to the standard
streams work correctly.

There's also the problem that sys.argv currently relies on the locale
encoding directly, because the filesystem encoding hasn't been worked out
at that point (see issue 8776). So this current change will also make
"print(sys.argv)" work more reliably in the POSIX locale.

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.
Date User Action Args
2014-04-28 17:11:25ncoghlansetrecipients: + ncoghlan, loewis, ishimoto, pitrou, vstinner, larry, jwilk, ezio.melotti, a.badger, r.david.murray, Sworddragon, python-dev, martin.panter, serhiy.storchaka, bkabrda
2014-04-28 17:11:25ncoghlanlinkissue19977 messages
2014-04-28 17:11:25ncoghlancreate