j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
On Tue, 31 Jul 2018 at 09:13 Victor Stinner email@example.com wrote:
Stupid question. Why not using Cython instead of a Cython-like which would have limitations and might be incompatible with Cython?
Do you mean add something to the CPython standard library?
Yes, what Eric is suggesting is a baseline tool like Cython be added to Python itself so it becomes the minimum, common tool that we point all extension authors to. Then Cython could build on top of that -- or the C API that the tool used -- so either tool can be used for the best situation. But the key point is that if we want as slick as Julia's FFI ( https://docs.julialang.org/en/stable/manual/calling-c-and-fortran-code/index...), then we will have to provide an FFI compiler for people to use in at least the simple cases.
2018-07-31 17:59 GMT+02:00 Eric Snow firstname.lastname@example.org:
Not that long ago Brett, Barry, and I were talking about how to get extension authors to move away from the C-API. Cython is the obvious choice, but it isn't an official tool nor does it necessarily make sense to make it one. Regardless, it would help all parties involved if there were an official tool that was part of CPython (i.e. in the repo). Cython could build on top of it and extension authors would be encouraged to use it or Cython. If such a thing makes sense, I figure we would follow the pattern set by asyncio (relative to twisted).
capi-sig mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org