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 vstinner
Date 2020-04-09.15:19:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586445596.83.0.583225080007.issue40241@roundup.psfhosted.org>
In-reply-to
Content
Similarly to bpo-39573 (PyObject) and bpo-40170 (PyTypeObject), I propose to make the PyGC_Head structure opaque in the C API.

See https://bugs.python.org/issue39573#msg361513 for the rationale. In short, my plan is to hide all implementation details from the C API.

The PyGC_Head structure caused ABI issues recently: bpo-39599 "ABI breakage between Python 3.7.4 and 3.7.5: change in PyGC_Head structure". Making the structure opaque would reduce the risk of such ABI issue. In fact, the reporter of bpo-39599 really require to access PyGC_Head structure to write a profiler, so this issue doesn't fix all use cases, but it should benefit to most people ;-) PyGC_Head structure will remain accessible via the internal C API which doesn't provide any backward compatibility warranty.
History
Date User Action Args
2020-04-09 15:19:56vstinnersetrecipients: + vstinner
2020-04-09 15:19:56vstinnersetmessageid: <1586445596.83.0.583225080007.issue40241@roundup.psfhosted.org>
2020-04-09 15:19:56vstinnerlinkissue40241 messages
2020-04-09 15:19:56vstinnercreate