A new C API: enabling Python's evolution; binary compatible across many versions of CPython, PyPy & GraalVM; easy to debug; as fast or faster than the old API
Here's the recording of the HPy presentation that HPy core dev @timfelgentreff gave at the @ICOOOLPS and TRUFFLE workshops last week: https://t.co/A4ZRbYU0VB
Mark Shannon @hotpyguy talk: "I still don't know what the C-API is, and I've been trying for years!" Long discussion about how to fix the Python C API, what is the C API, what are the issues, etc.
@anthonypjshaw I wrote the appendix B for this translated version :)
The title is <The future of CPython through performance issues>
Briefly explained
- JIT implementation history and PEP 659
- Multicore issues (subinterpreter, nogil..)
- C API (and hpy)
We'll do our first HPy Twitch stream today (September 22)! At 15:00 CEST https://t.co/Qyfn7J34n6
@timfelgentreff will do a quick presentation about the HPy goals and motivation, and then talk about the current status. Afterwards there will be a discussion.
Come join us!
We'll do our first HPy Twitch stream today (September 22)! At 15:00 CEST https://t.co/Qyfn7J34n6
@timfelgentreff will do a quick presentation about the HPy goals and motivation, and then talk about the current status. Afterwards there will be a discussion.
Come join us!
Interesting discussion on the future of the CPython C API and stable ABI, on the CPython discourse: https://t.co/bR3ANZkSsQ
mentions HPy a bunch of times
There will be an HPy BoF session with the title "HPy: Where next?" with @antocuni and @hodgestar at the SciPy conference @scipyconf in Austin next Friday (July 15, 4:40-5:35pm, Room 101). Join us there!
https://t.co/etY3EgVmOp