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 christian.heimes
Recipients alex, christian.heimes, erlendaasland, petr.viktorin, pitrou, serhiy.storchaka, skrah, vstinner
Date 2021-12-08.15:59:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638979147.02.0.151936511514.issue45459@roundup.psfhosted.org>
In-reply-to
Content
I thought of a version field, too. In the end it is going to cause more work and trouble than it would benefit us.

Stack-allocated Py_buffer's are typically initialized with

   Py_buffer data = {NULL, NULL};

. The code initializes Py_buffer.buf and Py_buffer.obj as NULL. The remaining fields are whatever random values happens to be on the C stack. If we would append a version field to the struct, than every project would have to initialize the field properly.
History
Date User Action Args
2021-12-08 15:59:07christian.heimessetrecipients: + christian.heimes, pitrou, vstinner, alex, petr.viktorin, skrah, serhiy.storchaka, erlendaasland
2021-12-08 15:59:07christian.heimessetmessageid: <1638979147.02.0.151936511514.issue45459@roundup.psfhosted.org>
2021-12-08 15:59:07christian.heimeslinkissue45459 messages
2021-12-08 15:59:06christian.heimescreate