Python C API, PyPy and the road into the future
I strongly disagree with the author's assertions that the need for better C API support is strictly a need for integrating with "legacy applications".The fact of the matter is that a vast array of systems-level software and high-performance software is only available via a C API interface.  New or old, that's still true today.I've used ctypes and I've used cffi; I'm glad they exist, but authors of popular packages often don't have the luxury of supporting both of them and the CPython API.If by legacy, they're attempting to paint the CPython API as the legacy one, I also find that a misleading argument at best.  PyPy is not yet the official future of Python, and attempting to paint themselves as the successor without any clear indicator of support for that future from the Python leadership seems odd.I'm all for them getting financial support they need to do the work, but attempting to justify that work by claiming only "legacy" applications need it seems uninformed at best.