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 jpe
Recipients Mark.Shannon, Xtrem532, erlendaasland, hroncok, jpe, pablogsal, petr.viktorin, rhettinger, scoder, vstinner
Date 2021-09-20.14:36:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Is adding the field back an option at this point? It would mean that extensions compiled against the release candidates may not be binary compatible with the final release

My take is that use_tracing is an implementation and version dependent field, and that binary compatibility will be maintained for a specific release (e.g. 3.10) but that there's no assurance that it will be there in the next release -- though these things tend not to change. I also regard generated cython code as only being valid for the releases that a specific cython version supports.

Code and API's change slowly, but eventually they do change.
Date User Action Args
2021-09-20 14:36:31jpesetrecipients: + jpe, rhettinger, scoder, vstinner, petr.viktorin, Mark.Shannon, hroncok, pablogsal, erlendaasland, Xtrem532
2021-09-20 14:36:31jpesetmessageid: <>
2021-09-20 14:36:31jpelinkissue43760 messages
2021-09-20 14:36:31jpecreate