Message122490
| Author |
belopolsky |
| Recipients |
Rhamphoryncus, amaury.forgeotdarc, belopolsky, eric.smith, ezio.melotti, lemburg, loewis, pitrou, vstinner |
| Date |
2010年11月27日.00:31:34 |
| SpamBayes Score |
5.537125e-05 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTinfuv-UvuiML=PBCc0390gWpq_-rPb=d3n1qwDi@mail.gmail.com> |
| In-reply-to |
<1290817625.25.0.105793802375.issue10542@psf.upfronthosting.co.za> |
| Content |
On Fri, Nov 26, 2010 at 7:27 PM, Eric Smith <report@bugs.python.org> wrote:
..
>
> In addition to the proposed Py_UNICODE_NEXT and Py_UNICODE_PUT_NEXT, > str.__format__ would also need a function that tells it how many Py_UNICODEs
> are needed to store a given Py_UCS4.
Yes, this functionality is currently hidden in
unicode_aswidechar(PyUnicodeObject *unicode,
wchar_t *w,
Py_ssize_t size):
/* Helper function for PyUnicode_AsWideChar() and
PyUnicode_AsWideCharString():
convert a Unicode object to a wide character string.
- If w is NULL: return the number of wide characters (including the
nul
character) required to convert the unicode object. Ignore size argument.
.. */
and I believe is reimplemented in a few other places. |
|