Message 408023 - Python tracker

➜

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	vstinner
Recipients	alex, christian.heimes, erlendaasland, petr.viktorin, pitrou, serhiy.storchaka, skrah, vstinner
Date	2021-12-08.15:20:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1638976810.81.0.785869827937.issue45459@roundup.psfhosted.org>
In-reply-to

Content
Would it make sense to add a "version" member to the structure? It would allow to support an old stable structure for the stable ABI and a new structure with other changes. The problem is how to initalize the version member. On Windows, many structures have a member which is the size of the structure. I tried to implement such ABI compatibility for PEP 587 PyConfig structure, but the idea was rejected (there was no need for a stable ABI when Python is embedded in an application): https://mail.python.org/archives/list/python-dev@python.org/thread/C7Z2NA2DTM3DLOZCFQAK5A2WFYO3PHHX/

Would it make sense to add a "version" member to the structure?

It would allow to support an old stable structure for the stable ABI and a new structure with other changes. The problem is how to initalize the version member. On Windows, many structures have a member which is the size of the structure.

I tried to implement such ABI compatibility for PEP 587 PyConfig structure, but the idea was rejected (there was no need for a stable ABI when Python is embedded in an application):
https://mail.python.org/archives/list/python-dev@python.org/thread/C7Z2NA2DTM3DLOZCFQAK5A2WFYO3PHHX/

History
Date	User	Action	Args
2021-12-08 15:20:10	vstinner	set	recipients: + vstinner, pitrou, christian.heimes, alex, petr.viktorin, skrah, serhiy.storchaka, erlendaasland
2021-12-08 15:20:10	vstinner	set	messageid: <1638976810.81.0.785869827937.issue45459@roundup.psfhosted.org>
2021-12-08 15:20:10	vstinner	link	issue45459 messages
2021-12-08 15:20:10	vstinner	create