Hugo van Kemenade

hugovk.dev

04 July 2026 23:46

step 1: do an experimental JIT step 2: do a website called www.doesjitgobrrr.com to track performance step 3: write a PEP called "JIT Go Brrr" step 4: non-experimental JIT gone brrr? step 5: CPython gone brr? step 6: brrrrrr? peps.python.org/pep-0836/ #Python #CPython #JIT #PEP #PEP836 #JIT #GoBrrr

Brett Cannon

snarky.ca

22 April 2026 19:20

PEP 832: virtual environment discovery discuss.python.org/t/106998 This PEP also puts me in a tie with @vstinner.bsky.social for being the 4th most prolific PEP (co-)author. 😅

PyCon US

pycon.us

13 April 2026 22:35

🔑 Security Track Spotlight: Python isn’t supposed to segfault… right? 👀 At #PyConUS 2026, @emmatyping.dev explores how Rust for CPython can improve memory safety and reliability in Python’s core runtime. #security us.pycon.org/2026/schedul...

Savannah Ostrowski

savannah.dev

13 April 2026 22:34

Frame pointers? Frame pointers! peps.python.org/pep-0831/

Pablo Galindo Salgado

pablogsal.com

13 April 2026 21:46

@lukasz.langa.pl has been an extraordinary example of how a program like the developer in residence can make Open Source sustainable and healthy. I don’t think I will surprise anyone saying that program has been successfully in great part because of him. He leaves very big shoes to fill! 🖤🙏