The Steering Council would like the C API WG to affirm their position (even if it’s that the WG cannot reach agreement) on PEP 793 before the September sprint in Cambridge [UK] with the goal of collectively pronouncing on it by the end of the sprint. Our preference is to delegate this decision to the WG, but we do feel a sense of urgency as this impacts the future roll out of free-threading. If not this PEP, we would like to have a viable alternative, as we feel that doing nothing in this area is worse.
Barring a pronouncement on PEP 793 by the WG in this time frame the SC may opt to make the decision on its own.
We realize the above WG position could also mean discussing and deciding on a direction for the future of the ABI (e.g. abi4, abi3t) for 3.15. The SC does not want to block PEP 793 on that being settled, we just recognize that if we did adopt a new ABI it could wind up making PEP 793 sort of immediately obsolete or unnecessary. That outcome should not be considered a problem. Any abi4 style declaration would be its own separate PEP, and could include “we no longer need PEP 793 which hasn’t been released yet” if this happened in the same 3.15 pre-beta release time frame.
Donghee
on behalf of the Steering Council