Serhiy Storchaka added the comment: A simplest solution is to raise a TclError instead of ValueError for non-BMP characters. This should not break any existing code, because a user code should be ready to catch a TclError in any case. Here is a patch.
A more complicated solution is to add ValueError to any catch of TclError. And this will fix only IDLE, user programs should fix self every. Also we can silently encode non-BMP characters for Tcl with UTF-16 (and decode a result back). This can cause some subtle errors with shifted indices however. ---------- keywords: +patch nosy: +serhiy.storchaka versions: +Python 2.7 Added file: http://bugs.python.org/file28376/tkinter_nobmp_error.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13153> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
