Message 177812 - Python tracker

➜

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	serhiy.storchaka
Recipients	JBernardo, Rosuav, asvetlov, ezio.melotti, ned.deily, roger.serwy, serhiy.storchaka, terry.reedy
Date	2012-12-20.12:57:02
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2012-12-20 12:57:02	serhiy.storchaka	set	recipients: + serhiy.storchaka, terry.reedy, ned.deily, ezio.melotti, roger.serwy, asvetlov, JBernardo, Rosuav
2012-12-20 12:57:02	serhiy.storchaka	set	messageid: <[email protected]>
2012-12-20 12:57:02	serhiy.storchaka	link	issue13153 messages
2012-12-20 12:57:02	serhiy.storchaka	create