On 22Feb2019 1008, Antoine Pitrou wrote:
Le 22/02/2019 à 18:17, Victor Stinner a écrit :
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.
I agree, these all sound like worthwhile PEPs.
Hopefully once we have some categorisations for where the current APIs are at, it will be easier to discuss the various proposals.
In particular, I think PEP D will have a lot of different ideas, and being able to compare them equivalently will be very important.
(And specifically on PEP A - I hear a lot of people say "check the top 10/20/30 C extensions", but I don't actually know what they are? Even just a list of them would be great! And I bet 10 of them are the ones included in CPython ;) )
Cheers, Steve