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 pitrou
Recipients ajaksu2, amaury.forgeotdarc, collinwinter, ezio.melotti, jafo, jimjjewett, lemburg, orivej, pitrou, vstinner
Date 2009-06-02.14:12:47
SpamBayes Score 8.41161e-05
Marked as misclassified No
Message-id <1243952101.5426.15.camel@localhost>
In-reply-to <>
> The patch breaks C API + binary compatibility for an essential Python
> type - that's not something you can easily undo.

I don't see how it breaks C API compatibility. No officially documented
function has changed, and the accessor macros still work. Am I missing

As for binary compatibility, yes, it does break it, which isn't an
exceptional situation in the development process. We have changed other
"essential types" too -- for example, recently, the PyLong object got
30-bit digits on some systems. Why you think it is hard to undo, I don't

As for the future ABI PEP, which has not yet been accepted, it does not
mention PyUnicodeObject as part of the structures which are guaranteed
to remain binary-compatible :
Date User Action Args
2009-06-02 14:12:50pitrousetrecipients: + pitrou, lemburg, collinwinter, jafo, jimjjewett, amaury.forgeotdarc, vstinner, ajaksu2, orivej, ezio.melotti
2009-06-02 14:12:49pitroulinkissue1943 messages
2009-06-02 14:12:47pitroucreate