➜

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 gpolo
Recipients gpolo, kbk, nnorwitz, ocean-city
Date 2008-12-01.17:45:16
SpamBayes Score 6.646689e-11
Marked as misclassified No
Message-id <1228153517.92.0.189591234799.issue1028@psf.upfronthosting.co.za>
In-reply-to
Content 
Some more clarifications about this bug:

Tcl shouldn't be giving us a UTF-8 string with a 0xC0 byte, since that
is not valid UTF-8. I'm aware that Tcl uses the sequence 0xC0 0x80 for
special purposes but it is also said that such sequences shouldn't be
passed as is when exported.

This bug doesn't affect python 2.x because it uses PyString_FromString
to convert such value to a Python string, where python 3.x uses
PyUnicode_FromString which assumes that it is receiving a valid utf-8
string but it turns out that is not always the case here.

It is indeed related to tk 8.4, but not sure which ones exactly (I hit
it with tk 8.4.19).
History
Date User Action Args
2008-12-01 17:45:18gpolosetrecipients: + gpolo, nnorwitz, kbk, ocean-city
2008-12-01 17:45:17gpolosetmessageid: <1228153517.92.0.189591234799.issue1028@psf.upfronthosting.co.za>
2008-12-01 17:45:17gpololinkissue1028 messages
2008-12-01 17:45:16gpolocreate