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 loewis
Recipients gvanrossum, lemburg, loewis, r.david.murray, scoder, stutzbach, vstinner, zooko
Date 2010-05-08.13:07:45
SpamBayes Score 1.2648e-06
Marked as misclassified No
Message-id <>
I propose a different approach:

1. add a flag to PyModuleDef, indicating whether the module was built in UCS-2 or UCS-4 mode. Then let the interpreter refuse the load the module, instead of having the dynamic linker do so.
2. provide a mode for the header files where Py_UNICODE is not defined. add another flag to PyModuleDef indicating whether that mode was used when compiling the extension.

Module authors then can make a choice whether or not to refer to the Unicode internal representation in their module. If they do, a UCS-2 version won't load into a UCS-4 interpreter. If they don't refer to Py_UNICODE at all, the module can be used across the two modes.

There is a slight risk that a module may already crash before calling PyModule_Create. To prevent that, we need to specify that no Unicode API must be used before calling PyModule_Create.
Date User Action Args
2010-05-08 13:07:49loewissetrecipients: + loewis, lemburg, gvanrossum, zooko, scoder, vstinner, stutzbach, r.david.murray
2010-05-08 13:07:48loewissetmessageid: <>
2010-05-08 13:07:46loewislinkissue8654 messages
2010-05-08 13:07:45loewiscreate