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 random832
Recipients eryksun, kbk, random832, roger.serwy, serhiy.storchaka, steven.daprano, terry.reedy, Árpád Kósa
Date 2015-11-23.18:05:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I can't reproduce without pickle. I did some further digging, though, and it *looks like*...

1. Pickle causes the built-in UTF-8 representation of a string to be populated, whereas encode('utf-8') does not. Can anyone think of any other operations that do this?
2. After the UTF-8 representation of the 2-character string is populated, concatenating a new character to it does not update or clear it.
3. However, it worked just fine with the 1-character string - concatenating it caused the UTF-8 representation to be cleared.

The actual operation that creates an inconsistent string is the concatenate operation, but it only happens with a string that has been "primed" by having its UTF-8 representation materialized.
Date User Action Args
2015-11-23 18:05:52random832setrecipients: + random832, terry.reedy, kbk, roger.serwy, steven.daprano, serhiy.storchaka, eryksun, Árpád Kósa
2015-11-23 18:05:52random832setmessageid: <>
2015-11-23 18:05:52random832linkissue25709 messages
2015-11-23 18:05:52random832create