Message145573
The current Windows build used 2-byte unicode chars because that is what Windows does. In 3.3, all builds will use a new unicode implementation that uses 1,2,or4 bytes as needed. But I suspect we will still have the paste problem unless we can somehow bypass the tk limitation.
Printing a Python string to the screen does not seem to involve conversion to a tk string. Or else tk blindly copies surrogate pairs to Windows even though it cannot create them.
In any case, true window-closing crashes (as opposed to an error traceback) are obnoxious bugs that we try to fix if possible. I verified this on my 64-bit Win 7 system. Thanks for the report. Feel free to look into the code if you can. |
|
Date |
User |
Action |
Args |
2011-10-15 00:02:00 | terry.reedy | set | recipients:
+ terry.reedy, ned.deily, ezio.melotti, JBernardo |
2011-10-15 00:02:00 | terry.reedy | set | messageid: <1318636920.5.0.330616995177.issue13153@psf.upfronthosting.co.za> |
2011-10-15 00:01:59 | terry.reedy | link | issue13153 messages |
2011-10-15 00:01:59 | terry.reedy | create | |
|