PEP 788 -- Protecting the C API from Interpreter Finalization

[ZeroIntensity]

Please consider PEP 788 -- Protecting the C API from Interpreter Finalization
https://peps.python.org/pep-0788/

This PEP was approved by the C API Working Group: capi-workgroup/decisions#70 (comment)

• The PEP has been discussed in threads listed in its Post-History header
• The PEP was announced on Discuss (link in Post-History)
• The PEP includes all relevant Suggested Sections
• The PEP includes endorsements from the projects/groups/people it helps
• The PEP has a CODEOWNERS entry

SIG-specific:

• Typing PEPs: link to the Typing Council's recommendation for the PEP:
• Packaging PEPs: don't file the issue here, ask the delegate (Paul Moore) on Packaging Discourse

[NicolasT]

Nit: I think there's a minor bug in the example code in the PEP, passing a const char * returned by PyUnicode_AsUTF8 to free.

[ZeroIntensity]

Yeah, initially that wasn't a call to PyUnicode_AsUTF8 and I just forgot to remove the free call when I changed it. Good catch!