Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

After cpyext and cffi, this is the third attempt, largely driven by PyPy people, to get a C-API that people want to use.

If they succeed and keep the CPython "leaders" who ruined the development experience and social structure of CPython out of PyPy, PyPy might get interesting. If they don't keep them out, those "leaders" will merrily sink yet another project.



cffi replaces ctypes, which is a completely different thing. cpyext is a reimplementation of the Python C-API, so no attempt at improving the API.

HPy on CPython uses the existing C-API under the hood, so there is zero need to build up some keep someone out...


cffi is used to wrap c libraries. Only a masochist would use ctypes to wrap a whole library. While both are technically FFIs, it does not make sense to compare them. From a conceptual perspective, cffi was written to replace the C-API for C modules.


Expand here on your use of double quotes and the subtext of your comment if you please.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: