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, larry, lemburg, loewis, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, terry.reedy, vstinner
Date 2013-12-09.22:50:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7dwa=QfcRUcQQtHoNM1uFfc7MdA0t7MQOxs94swdXeHEg@mail.gmail.com>
In-reply-to <1386585736.77.0.335520394132.issue19846@psf.upfronthosting.co.za>
Content
There's a wrong assumption here: glib applications on Linux use UTF-8
regardless of locale. That's the part I have a problem with: the assumption
that the locale will correctly specify the encoding to use for OS APIs on
modern Linux systems.

It's simply not always true: some Linux distros would be better handled
like OS X, where we always use UTF-8, regardless of what the locale says.
History
Date User Action Args
2013-12-09 22:50:02ncoghlansetrecipients: + ncoghlan, lemburg, loewis, terry.reedy, pitrou, vstinner, larry, a.badger, r.david.murray, Sworddragon, serhiy.storchaka, bkabrda
2013-12-09 22:50:02ncoghlanlinkissue19846 messages
2013-12-09 22:50:02ncoghlancreate