PEP 779: Criteria for supported status for free-threaded Python

The Steering Council has updated one paragraph of its earlier announcement to clarify terminology.

Original wording

1. C API/ABI compatibility and Stable C API for free-threading
Any proposed changes that break existing API or ABI guarantees must be agreed to in advance with the C API Working Group. The Steering Council also expects that Stable C APIs for free-threading should be prepared and defined for Python 3.15. These APIs must provide a reliable foundation so that third-party library maintainers, particularly those who rely on the C API, can plan their support with confidence.

Updated wording

1. C API/ABI compatibility and Stable ABI for free-threading
Any proposed changes that break existing API or ABI guarantees must be agreed to in advance with the C API Working Group. Limited C APIs for free-threading must provide a reliable foundation so that third-party library maintainers, particularly those who rely on the C API, can plan their support with confidence. The Steering Council also expects that Stable ABI for free-threading should be prepared and defined for Python 3.15.

Donghee, on behalf of the Steering Council

7 Likes