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 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.
History
Date User Action Args
2009-10-05 09:59:57amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, lemburg, Rhamphoryncus, vstinner, ezio.melotti, bupjae
2009-10-05 09:59:57amaury.forgeotdarcsetmessageid: <1254736797.38.0.885294853984.issue5127@psf.upfronthosting.co.za>
2009-10-05 09:59:55amaury.forgeotdarclinkissue5127 messages
2009-10-05 09:59:55amaury.forgeotdarccreate