DiscoverBehind the Commit
Behind the Commit
Claim Ownership

Behind the Commit

Author: Mia Bajić

Subscribed: 1Played: 36
Share

Description

Meet the people shaping open-source across Europe and beyond! Have you ever wondered who the people are behind the open source technologies you use every day? Behind the Commit explores the stories and technologies shaping open source across Europe—from the tools being built to the challenges of maintaining them in a constantly evolving ecosystem. We speak with maintainers about what they're building, why it matters, and how open source is changing in the age of AI.

25 Episodes
Reverse
In this episode, I'm chatting with Larry Hastings — CPython core developer, release manager for Python 3.4 and 3.5, creator of the Gilectomy (an attempt to remove the GIL years before free-threaded Python), and the person who added = inside f-strings and Argument Clinic to CPython. Free-threaded Python is arriving, and threaded code is hard to test: if four threads grab a lock, you don't know which one gets it first, so a race condition that shows up once in a thousand runs almost never shows up in your test suite. We talk about why the Gilectomy got slower with every core he added, Guido's bar for removing the GIL, and Blanket, Larry's library that makes threading tests deterministic. He also explains how he built it with AI doing most of the typing, and why he still reviews every line.Outline0:00 Meet Larry Hastings: from the Gilectomy to free-threaded Python0:57 Brett Cannon: 'Larry, do you want to be a core developer?'2:14 Free-threaded Python ships: what's different from 10 years ago?2:54 Why the Gilectomy failed: reference counting across threads3:54 More cores, slower Python4:49 Guido's bar for removing the GIL (and does free threading clear it?)5:43 How do you test free-threaded code?7:05 Four threads, one lock: which one gets it first?8:53 100% coverage vs a race condition that happens 1 in 1,000 runs9:26 How Blanket lets your test decide which thread wins10:08 The hardest part wasn't technical: designing the API12:41 'The GIL is a pair of crutches we need to throw away'14:25 Advice for code meeting free-threaded Python for the first time15:26 Pass your locks in as parameters (nobody likes monkey patching)16:14 Human-guided AI development: how Blanket was built17:06 AI's bad habits: 'I'm going to write a while loop and poll'17:38 Not vibe coding: pair programming with AI18:27 One session writes the proposal, two more review it19:47 Vibe-documented: 'make it sound like I wrote it'Episode links– Blanket on GitHub: https://github.com/larryhastings/blanket– Blanket on PyPI: https://pypi.org/project/blanket/– Larry Hastings on GitHub: https://github.com/larryhastings– Guido's Artima blog post on removing the GIL: https://www.artima.com/weblogs/viewpost.jsp?thread=214235
How do you maintain a Python package downloaded more than 40 million times every month, while working on it in your free time?In this episode of Behind the Commit, Mia talks with Daniel Moran, the solo maintainer of FakeRedis, a pure-Python Redis-compatible implementation used for testing, compatibility checks, and server-agnostic development.Daniel shares how FakeRedis grew from a personal solution into a widely used open-source project supporting Redis, Valkey, and Dragonfly. They also discuss maintaining a 73-variation CI matrix, AI-generated pull requests, avoiding burnout, monetizing a JetBrains GitHub Actions plugin, Django Commons, and his vision for FakeRedis becoming a standard in the ecosystem.Outline00:00 FakeRedis in numbers00:24 What is FakeRedis?02:32 Redis license changes04:48 New use cases06:21 Supporting Redis, Valkey, and Dragonfly07:50 The 73-variation test matrix10:45 Maintaining open source in your free time16:10 AI and open-source maintenance20:45 Building a JetBrains plugin24:42 Django Commons27:10 The future of FakeRedis29:19 Connect with DanielEpisode links – https://plugins.jetbrains.com/plugin/19347-github-actions-manager – GitHub Actions Manager Plugin – https://django-commons.org/ – Django Commons – https://www.linkedin.com/in/daniel-moran-8a096a15/ – Daniel's LinkedIn profile
From 1–2 million to over 40 million downloads per month. Explore 73 variations and discover the DragonFly flavor, its commands, and supported arguments.
In this episode, I'm chatting with Emily Morehouse — CPython core developer, former Python Steering Council member, PSF Fellow, and co-founder and director of engineering at Cuttlesoft. She holds three degrees in theater, computer science, and criminology, and picked up Python in college simply because it was more fun than C++.After Guido van Rossum announced at a Python conference that he wanted more women in CPython core development, she emailed Guido. He said yes and personally mentored her. She went on to implement the walrus operator (:=), one of the most controversial features in Python's history and one of the things that ultimately led Guido to step down as BDFL. She also chaired PyCon US for three years, two of which went fully online during the pandemic.Outline 0:00 Episode highlights 0:26 Introduction 1:02 "If someone told you 10 years ago you'd be a core developer…" 1:47 Three degrees: theater, CS, and criminology 1:54 Journey into core development 2:43 Guido's call for female core developers 3:08 "My husband was elbowing me in the side" 3:20 What were you afraid of? 3:57 She emailed Guido — and he said yes 4:34 First language summit: realizing experts are human 5:08 What it's actually like to be mentored by Guido 5:43 The async Friday ritual with Guido and Eric Snow 6:22 Why there's no low-hanging fruit in CPython 7:10 Implementing the Walrus operator (:=) 8:27 Support from the core developer community 8:32 How to inspire more people into core development 9:38 People still reach out years later 10:04 Chairing PyCon US through a pandemic 11:05 What community work teaches you about leadership 12:54 How parenthood changed her relationship with open source 13:59 Practical first steps to contribute to CPython 14:56 OutroEpisode links – CPython dev guide: https://devguide.python.org – Cuttlesoft: https://cuttlesoft.com – Emily on GitHub: https://github.com/emilyemorehouse
In this episode, I'm chatting with Emily Morehouse — CPython core developer, former Python Steering Council member, PSF Fellow, and co-founder and director of engineering at Cuttlesoft. She holds three degrees in theater, computer science, and criminology, and picked up Python in college simply because it was more fun than C++.After Guido van Rossum announced at a Python conference that he wanted more women in CPython core development, she emailed Guido. He said yes and personally mentored her. She went on to implement the walrus operator (:=), one of the most controversial features in Python's history and one of the things that ultimately led Guido to step down as BDFL. She also chaired PyCon US for three years, two of which went fully online during the pandemic.Full episode coming soon!
loading
Comments