Message199474
| Author |
pitrou |
| Recipients |
barry, christian.heimes, kristjan.jonsson, pitrou, ronaldoussoren, serhiy.storchaka, vstinner |
| Date |
2013年10月11日.13:23:51 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<681666985.69194707.1381497804258.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to |
<1381497054.83.0.689078566159.issue19219@psf.upfronthosting.co.za> |
| Content |
> Sorry for sarcasm.
Well, indeed, the sarcasm is undeserved here, if the interpreter cannot
crash because of the change.
> > It's exactly what you suggest: reuse PyUnicode_AsUTF8String().
>
> Actually _PyUnicode_UTF8(). PyUnicode_AsUTF8String() creates UTF8
> cache if it is not exists and this can be not desired. We could use
> this optimization in many other places, in particular in
> PyUnicode_AsUTF8String() itself.
I don't understand how _PyUnicode_UTF8() can be used for *unmarshalling*. |
|