Message149594
| Author |
loewis |
| Recipients |
Jim.Jewett, docs@python, loewis, vstinner |
| Date |
2011年12月16日.05:41:30 |
| SpamBayes Score |
9.4262145e-09 |
| Marked as misclassified |
No |
| Message-id |
<4EEADA09.7080405@v.loewis.de> |
| In-reply-to |
<1323995670.92.0.499848201076.issue13604@psf.upfronthosting.co.za> |
| Content |
> Why is the utf-8 representation not cached when it is generated for
> ParseTuple et alia?
It is.
> When a string is created from a wchar_t array, who is responsible for
> releasing the original wchar_t array?
The caller.
> 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. |
|