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 belopolsky
Recipients antlong, belopolsky, jkloth, ronaldoussoren
Date 2010-07-23.04:18:52
SpamBayes Score 0.00028015528
Marked as misclassified No
Message-id <1279858744.26.0.168086003551.issue9335@psf.upfronthosting.co.za>
In-reply-to
Content
This is clearly a Tkinter rather than Mac issue, so I am unassigning this from Ronald.  This appears to be the same problem as the one Mark described in msg102301.

>>> import locale
>>> locale.nl_langinfo(locale.CODESET)
'US-ASCII'
>>> import _tkinter
>>> locale.nl_langinfo(locale.CODESET)
'UTF-8'

This happens in both 2.6 and 2.7, but seems to be deliberate.  As Mark wrote in msg102328:

"""
There's still the issue of the Tkinter import changing the locale, but that seems to be out of Python's control.  As far as I can tell, it happens when the module initialization calls Tcl_FindExecutable, which is part of the Tcl library itself.  This may well be deliberate:  see

http://www.tcl.tk/cgi-bin/tct/tip/66.html
"""

What is still unclear to me, is why after CODESET changes to 'UTF-8', 2.6 thinks that '\xff' is a letter, but 2.7 does not.

Of course, '\xff' makes little sense in 'UTF-8', but why does the answer change between versions?
History
Date User Action Args
2010-07-23 04:19:04belopolskysetrecipients: + belopolsky, ronaldoussoren, jkloth, antlong
2010-07-23 04:19:04belopolskysetmessageid: <1279858744.26.0.168086003551.issue9335@psf.upfronthosting.co.za>
2010-07-23 04:18:52belopolskylinkissue9335 messages
2010-07-23 04:18:52belopolskycreate