➜

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 aronacher
Recipients aronacher
Date 2011-03-16.17:26:33
SpamBayes Score 6.056202e-07
Marked as misclassified No
Message-id <1300296395.6.0.964785890032.issue11574@psf.upfronthosting.co.za>
In-reply-to
Content 
Right now Python happily falls back to ASCII if it can not parse your LC_CTYPE or something similar happens.  Instead of falling back to ASCII it would be better if it falls back to UTF-8.

Alternatively it should at least give a warning that it's falling back to ASCII.

This issue was discussed at PyCon and the consensus so far was that falling back to UTF-8 in 3.3 might be a good idea and should not break much code as UTF-8 is a superset of ASCII.
History
Date User Action Args
2011-03-16 17:26:35aronachersetrecipients: + aronacher
2011-03-16 17:26:35aronachersetmessageid: <1300296395.6.0.964785890032.issue11574@psf.upfronthosting.co.za>
2011-03-16 17:26:33aronacherlinkissue11574 messages
2011-03-16 17:26:33aronachercreate