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 poolie
Recipients benjamin.peterson, gz, pitrou, poolie, r.david.murray, vstinner
Date 2011-12-21.01:18:07
SpamBayes Score 2.3702747e-05
Marked as misclassified No
Message-id <CAA9uavBkvO46_pPpKfgRpXO_J4buo_odd0K=OL3TOM69QHvuhw@mail.gmail.com>
In-reply-to <4EF12EBF.7020809@haypocalc.com>
Content
Thanks for the example.

Like you say, realistically, all data exchanged with other programs
and with the system needs to be in the same encoding.  (User document
content may be in something else.)

On modern systems, this problem is solved by making the standard
encoding UTF-8.  So it is unfortunate that, when no locale is set,
Python3 defaults to ascii for the filesystem.

With no locale set, python3 makes getdefaultencoding() utf-8, so it
seems oddly pessimistic to make the fsencoding only ascii.

If someone really wants to run everything in iso-8859-1 this patch
would not stop them doing so.
History
Date User Action Args
2011-12-21 01:18:09pooliesetrecipients: + poolie, pitrou, vstinner, benjamin.peterson, r.david.murray, gz
2011-12-21 01:18:08poolielinkissue13643 messages
2011-12-21 01:18:07pooliecreate