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: https://github.com/capi-workgroup/decisions/issues/70#issuecomment-3079052379 * [x] The PEP has been discussed in threads listed in its `Post-History` header <!-- You can add extra discussion links here, e.g. to individual comments. --> * [x] The PEP was announced on [Discuss](https://discuss.python.org/c/peps/19) (link in `Post-History`) <!-- Generally you should wait about a week for people to react there before filing this issue. --> * [x] The PEP includes all relevant [Suggested Sections](https://peps.python.org/pep-0012/#suggested-sections) * [ ] The PEP includes endorsements from the projects/groups/people it helps <!-- e.g. if you say “this feature would help NumPy”, back it up with a statement from NumPy developers --> * [x] The PEP has a CODEOWNERS entry <!-- https://github.com/python/peps/blob/main/.github/CODEOWNERS --> SIG-specific: * [ ] *Typing* PEPs: link to the [Typing Council](https://github.com/python/typing-council)'s recommendation for the PEP: * [ ] *Packaging* PEPs: don't file the issue here, ask the delegate (Paul Moore) on [Packaging Discourse](https://discuss.python.org/c/packaging/14) <!-- Thank you for your proposal to improve Python! -->
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)
Post-HistoryheaderPost-History)SIG-specific: