Le 22/02/2019 à 18:17, Victor Stinner a écrit :
Last months, I was busy to fill https://pythoncapi.readthedocs.io/ website with random notes. Many discussions occurred on this list and python-dev, but I was only able to make the most simple and least controversal changes in Python upstream. I didn't write a PEP because CPython had a governance crisis. Since a new Steering Committee has been elected, it's time to see how concrete PEP can be written.
IMHO we need to split the giant "C API" problem into multiple PEPs. I propose 4 PEPs:
PEP A: Ecosystem of C extensions in 2019
+1. Sounds like a good start.
PEP B: Define good and bad C APIs
I'm not sure the "good" vs "bad" categorization will lead to very productive discussions. I think Steve's categorization proposal is more likely to bridge the various opinions on the subject.
PEP C: Plan to enhance the existing C API
Sounds ok, though of course it depends on whatever the resulting proposal looks like ;-)
PEP D: Completely new C API
Sounds interesting too, if more adventurous.