"C API: this was a follow up of what we discussed at the C API summit at EuroPython. The current C API is problematic, so we are exploring ideas for the development of PyNI (Python Native Interface), whose design will likely be heavily inspired by HPy. It's important to underline that this is just the beginning and the entire process will require multiple PEPs."
"fancycompleter This is a small PR which I started months ago, to enable colorful tab completions within the Python REPL. I wrote the original version of fancycompleter 15 years ago, but colorful completions work only in combination with PyREPL. Now PyREPL is part of the standard library and enabled by default, so we can finally upstream it. I hope to see it merged soon."
"" JIT stuff": I spent a considerable amount of time talking to the people who are working on the CPython JIT (in particular Mark, Brandt, Savannah, Ken Jin and Diego). Knowledge transfer worked in both ways: I learned a lot about the internal details of CPython's JIT, and conversely I shared with them some of the experience, pain points and gut feelings which I got by working many years on PyPy."
A CPython Core Developer Sprint in Cambridge gathered about fifty core developers and guests hosted by ARM. Three primary focus areas emerged: redesigning the problematic C API toward a PyNI inspired by HPy and requiring multiple PEPs; upstreaming colorful tab completions via fancycompleter now that PyREPL is in the standard library; and intensive knowledge exchange on CPython's tracing JIT with PyPy veterans. CPython's JIT and PyPy's JIT share tracing fundamentals. Real-world Python workloads differ from pyperformance benchmarks, and practical JIT optimization requires addressing real application pain points and lessons learned.
Read at Antocuni
Unable to calculate read time
Collection
[
|
...
]