PEP 788: Protecting the C API from Interpreter Finalization

PEPs
41

@ZeroIntensity

The Steering Council is generally positive about the newly revised PEP 788 and expects to approve it, unless there are major objections from the C API WG or from the binding ecosystem perspective.

If no major objections are raised by AoE on April 27, 2026, we plan to formally approve the PEP next week.

Revised records

Warm regards,
Donghee
on behalf of the Python Steering Council

Cross-posted from: PEP 788: Protecting the C API from Interpreter Finalization · Issue #70 · capi-workgroup/decisions · GitHub

(2026-04-18) The veto timeline has been updated: PEP 788: Protecting the C API from Interpreter Finalization - #43 by corona10

5 Likes
42

@vstinner @encukou @steve.dower @storchaka @erlendaasland(as C API WG)

@ngoldbaum @wjakob (as binding ecosystems)

If the C API WG or members of the binding ecosystem have any major objections or concerns, please either raise them in the thread or send them to steering-council@python.org.
We will review any such feedback before the final official approval.

Warm regards,
Donghee
on behalf of the Python Steering Council

2 Likes
43

Hi,

SC have decided to move the veto timeline announced in the original post up from May 1 to April 27 AoE. This reflects internal discussion that, if the PEP is officially approved, the implementer should have enough time to proceed with the implementation before the beta cutoff (May 5).

I also want to apologize for any confusion caused, especially since I was the one who made the original post.

Warm regards,
Donghee
on behalf of the Python Steering Council

cc @vstinner @encukou @steve.dower @storchaka @erlendaasland @ngoldbaum @wjakob

6 Likes
44

Given that we have received no concerns from the C API WG or from the binding ecosystem,
the SC is happy to accept the PEP.

Congratulations, @ZeroIntensity .

Warm regards,
Donghee
on behalf of the Python Steering Council

7 Likes