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 terry.reedy
Recipients JBernardo, ezio.melotti, ned.deily, terry.reedy
Date 2011-10-15.00:01:59
SpamBayes Score 3.0604536e-10
Marked as misclassified No
Message-id <1318636920.5.0.330616995177.issue13153@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2011-10-15 00:02:00terry.reedysetrecipients: + terry.reedy, ned.deily, ezio.melotti, JBernardo
2011-10-15 00:02:00terry.reedysetmessageid: <1318636920.5.0.330616995177.issue13153@psf.upfronthosting.co.za>
2011-10-15 00:01:59terry.reedylinkissue13153 messages
2011-10-15 00:01:59terry.reedycreate