Author lemburg
Recipients Rhamphoryncus, amaury.forgeotdarc, bupjae, ezio.melotti, lemburg, vstinner
Date 2010-01-08.21:26:52
SpamBayes Score 8.70108e-09
Marked as misclassified No
Message-id <1262986015.58.0.297444713155.issue5127@psf.upfronthosting.co.za>
In-reply-to
Content
I don't see the point in changing the various conversion APIs in the unicode database to return Py_UCS4 when there are no conversions that map code points between BMP and non-BMP.

In order to solve the problem in question (unicode_repr() failing), we should change the various property checking APIs to accept Py_UCS4 input data. This needlessly increases the type database size without real benefit.

For that to work properly we'll have to either make sure that extensions get recompiled if they use these changed APIs, or we provide an additional set of UCS2 APIs that extend the Py_UNICODE input value to a Py_UCS4 value before calling the underlying Py_UCS4 API.
History
Date User Action Args
2010-01-08 21:26:55lemburgsetrecipients: + lemburg, amaury.forgeotdarc, Rhamphoryncus, vstinner, ezio.melotti, bupjae
2010-01-08 21:26:55lemburgsetmessageid: <1262986015.58.0.297444713155.issue5127@psf.upfronthosting.co.za>
2010-01-08 21:26:53lemburglinkissue5127 messages
2010-01-08 21:26:52lemburgcreate