Use the limited C API for some of our stdlib C extensions

I like this proposal both to EOODF and to debug problems with the limited API early. Doing so also provides a good example for other extension module authors, and maybe even makes a potential future splitting up of the stdlib easier [1].

Is there a PEP or other document about the criteria for what goes in the limited C API or not? I’m not looking for a list, but just a set of general principles that can be applied when asking what should get added, or even what should get removed?


  1. because PyPI stdlib extension modules could publish abi3 binaries ↩︎

4 Likes