Message93587
| Author |
amaury.forgeotdarc |
| Recipients |
Rhamphoryncus, amaury.forgeotdarc, bupjae, ezio.melotti, lemburg, vstinner |
| Date |
2009年10月05日.09:59:55 |
| SpamBayes Score |
6.208682e-05 |
| Marked as misclassified |
No |
| Message-id |
<1254736797.38.0.885294853984.issue5127@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> No, but changing the APIs from 16-bit integers to 32-bit integers
> does require a recompile of all code using it.
Is it acceptable between 3.1 and 3.2 for example? ISTM that other
changes already require recompilation of extension modules.
> Also, the Unicode type database itself uses Py_UNICODE, so
> case mapping would fail for non-BMP code points.
Where, please? in unicodedata.c, getuchar and _getrecord_ex use Py_UCS4. |
|