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 barry, paul.moore, pitrou, steve.dower, tim.golden, zach.ware
Date 2017-12-20.17:27:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513790879.02.0.213398074469.issue32388@psf.upfronthosting.co.za>
In-reply-to
Content
See original discussion on python-dev:
https://mail.python.org/pipermail/python-dev/2017-December/151328.html

Summary: binary compatibility for C extensions which don't use the stable ABI is currently "best effort" and uses distinguished flags in the tp_flags field of type objects to indicate whether a field is physically present or not.  Unfortunately, tp_flags is 32 bits and therefore a scarce resource.  Also, binary compatibility is 1) not guaranteed anyway 2) of less use nowadays.

So we propose to remove the binary compatibility requirement when creating static type objects (i.e. not using the stable ABI).
History
Date User Action Args
2017-12-20 17:27:59pitrousetrecipients: + pitrou, barry, paul.moore, tim.golden, zach.ware, steve.dower
2017-12-20 17:27:59pitrousetmessageid: <1513790879.02.0.213398074469.issue32388@psf.upfronthosting.co.za>
2017-12-20 17:27:58pitroulinkissue32388 messages
2017-12-20 17:27:58pitroucreate