You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2017-06-23.07:44:06.025>created_at=<Date2012-03-15.19:15:20.647>labels= ['expert-IDLE', 'type-feature']
title='IDLE - allow shell to support different locales'updated_at=<Date2017-06-23.07:44:06.024>user='https://github.com/serwy'
Per Martin's request, this issue has been separated from bpo-14200.
The IDLE shell presently has an effective locale of "BMP UTF8" due to a limitation in Tkinter, described in bpo-12342.
IDLE should support different output codecs, like "ascii" and "utf8". In order to work around Tkinter's limitations, unsupported characters would be replaced (this is related to bpo-14304).
This amounts to adding some extra code to OutputWindow's write() to raise encoding errors if the string contains unsupported characters.
I do not understand this issue. Locales (the title) and codecs (the message) are different things. A Tk Text widget, with Idle's wrapper, is essentially a BMP terminal. That is one thing that makes Idle's Shell better than Window's command prompt. An ascii codec would add to tk's limitations, not work around them. bpo-14304 does what I think is needed.
Pending some clarification of the proposal and benefits, I think this should be closed.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: