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 Jim.Jewett
Recipients Jim.Jewett, docs@python, loewis, vstinner
Date 2011-12-16.13:50:16
SpamBayes Score 9.357737e-12
Marked as misclassified No
Message-id <>
>> Why is the utf-8 representation not cached when it is generated for
>> ParseTuple et alia?

My error -- I read something backwards.

>> When a string is created from a wchar_t array, who is responsible for
>> releasing the original wchar_t array?

> The caller.

OK, I'll document that.

>> As I read it now, Python
>> doesn't release the buffer, and the caller can't because maybe Python
>> just pointed to it as memory shared with the canonical
>> representation.

> But Python won't; it will always make a copy for itself.

I thought I found an example each way, but it is possible that the shared version was something python had already copied.  If not, I'll raise that as a separate issue to get the code changed.

(Note that I may not be able to look at this again until after Christmas, so I'm likely to go silent for a while.)
Date User Action Args
2011-12-16 13:50:21Jim.Jewettsetrecipients: + Jim.Jewett, loewis, vstinner, docs@python
2011-12-16 13:50:20Jim.Jewettsetmessageid: <>
2011-12-16 13:50:19Jim.Jewettlinkissue13604 messages
2011-12-16 13:50:19Jim.Jewettcreate