Uploaded August 2026 | Updated November 2026, 3 days ago
[EuroPython 2026 - S1 on 2026-07-15]
🎤 *Free-threaded Python: past, present and future by Thomas Wouters*
🔗 https://ep2026.europython.eu/session/free-threaded-python-past-present-and-future
📝 Abstract:
Free-threaded Python, the effort to remove the Global Interpreter Lock from CPython, is one of the biggest and most exciting changes to Python in many years. However, It can be hard to follow what that means, what effect it will have on you and your code, and how this isn't yet another Python 2 to 3 migration.
This overview will explain what free-threading is, why it's a big deal, how it differs from other ways to deal with the GIL, and what the plan is for ensuring a smooth migration. We'll explain the basics of thread safety, data races, and concurrent designs, how those apply to Python code, and how this will and won't change when the GIL is disabled. And yes, we'll show some threads go _brrr_.
Although we'll mention some complex, deeply technical problems, this is not a technical deep dive and any experience level is welcome.
---
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: creativecommons.org/licenses/by-nc-sa/4.0
[EuroPython 2026 - S1 on 2026-07-15]
🎤 *Free-threaded Python: past, present and future by Thomas Wouters*
🔗 https://ep2026.europython.eu/session/free-threaded-python-past-present-and-future
📝 Abstract:
Free-threaded Python, the effort to remove the Global Interpreter Lock from CPython, is one of the biggest and most exciting changes to Python in many years. However, It can be hard to follow what that means, what effect it will have on you and your code, and how this isn't yet another Python 2 to 3 migration.
This overview will explain what free-threading is, why it's a big deal, how it differs from other ways to deal with the GIL, and what the plan is for ensuring a smooth migration. We'll explain the basics of thread safety, data races, and concurrent designs, how those apply to Python code, and how this will and won't change when the GIL is disabled. And yes, we'll show some threads go _brrr_.
Although we'll mention some complex, deeply technical problems, this is not a technical deep dive and any experience level is welcome.
---
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: creativecommons.org/licenses/by-nc-sa/4.0

![Defending Open Source from AI Slop: A Maintainers Practical Guide
[EuroPython 2026 - S1 on 2026-07-17]
🎤 *Defending Open Source from AI Slop: A Maintainers Practical Guide by Sviatoslav Sydorenko (Святослав Сидоренко)*
🔗 https://ep2026.europython.eu/session/defending-open-source-from-ai-slop-a-maintainer-s-practical-guide
📝 Abstract:
Open source maintainers are drowning in a new kind of noise. AI-generated pull requests — superficial, poorly reasoned, and submitted without genuine understanding of the codebase — are consuming review bandwidth that was already scarce. These contributions range from cosmetic improvements that introduce subtle bugs to elaborate refactorings that no one asked for, all bearing telltale signs of LLM output: confident tone, plausible-looking code, and zero awareness of project conventions.
This talk presents a practical, battle-tested framework for combating AI slop without discouraging legitimate contributors. Drawing from real experiences maintaining pip-tools, aiohttp, ansible-core, CherryPy, and other Python projects, Ill share concrete strategies that work today.
First, well dissect the anatomy of AI slop PRs — what they look like, why they pass superficial review, and the hidden costs beyond wasted review time: CI compute waste, security risks from plausible-but-wrong code, and the demoralizing effect on genuine contributors who see low-effort submissions getting attention.
Then Ill walk through a defense-in-depth approach being developed across my projects: updating `CONTRIBUTING.md` with explicit expectations about understanding the codebase before submitting changes; crafting repository-level LLM instruction files (like `AGENTS.md`/`CLAUDE.md`) that steer AI tools toward project-specific conventions; configuring PR templates to require evidence of human reasoning; and establishing community norms that set quality expectations without being hostile to newcomers.
Well also tackle the harder questions: Where is the line between AI-assisted (the human drives and understands the change) and AI-generated (the human clicks submit on LLM output)? How do we preserve the welcoming culture that makes open source special while defending against low-effort spam? What should platforms like GitHub improve for maintainers?
Youll leave with a ready-to-adapt policy template and configuration files for your own projects.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: https://creativecommons.org/licenses/by-nc-sa/4.0/ Defending Open Source from AI Slop: A Maintainers Practical Guide](https://i.ytimg.com/vi/lDxaIKAUBoc/mqdefault.jpg)


![Stop Guessing, Start Understanding: How Arrow and Pandas Exchange Data
[EuroPython 2026 - S3A on 2026-07-17]
🎤 *Stop Guessing, Start Understanding: How Arrow and Pandas Exchange Data by Alenka Frim, Raúl Cumplido Domínguez*
🔗 https://ep2026.europython.eu/session/stop-guessing-start-understanding-how-arrow-and-pandas-exchange-data
📝 Abstract:
Pandas now natively supports PyArrow-backed data types. But what does that actually mean? If youve ever wondered how these two libraries relate to each other, whether they compete or complement each other, and what happens to your data when it moves between them, this talk is for you.
As PyArrow maintainers, we took on the challenge of digging into the conversion code between PyArrow and Pandas, and were here to share what weve learned. Well show you whats really going on under the hood: how Arrows columnar format differs from Pandas block-based memory layout (including what a BlockManager actually is), when data can be shared without copying, and when a full copy is unavoidable.
Well also clarify what each library is designed for and how they work together rather than against each other. With pandas increasingly adopting PyArrow as a backend, understanding this relationship is becoming essential rather than optional.
This talk is aimed at Python developers and data engineers who want to deepen their understanding of whats happening beneath the surface.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: https://creativecommons.org/licenses/by-nc-sa/4.0/ Stop Guessing, Start Understanding: How Arrow and Pandas Exchange Data](https://i.ytimg.com/vi/lnEA4ACO2yo/mqdefault.jpg)



![How to build a cross-platform graphical user interface with Python — Russell Keith-Magee
[EuroPython 2025 — Terrace 2B on 2025-07-18]
🎤 *How to build a cross-platform graphical user interface with Python by Russell Keith-Magee*
🔗 https://ep2025.europython.eu/session/how-to-build-a-cross-platform-graphical-user-interface-with-python
📝 Abstract:
If you need to build a user interface for your Python code, many guides will tell you that your only options are to use the command line, or wrap your code in a web interface. However, there is another option - building a native GUI interface. In fact for some use cases, a GUI app may be your _only_ option.
In this talk, youll learn how to build and run a graphical user interface (GUI) that can run on your desktop, on your phone, or in a browser. Youll learn how you can use the BeeWare suite of tools to bootstrap a new GUI project, develop a GUI interface, and deploy that app to multiple desktop and mobile platforms, without making any code changes. Youll learn how to access device hardware like GPS and cameras; and youll learn how to distribute your application - including all runtimes and third-party libraries - to others. Lastly, youll get a brief introduction to how you can access native platform APIs that dont have a Python API.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: https://creativecommons.org/licenses/by-nc-sa/4.0/ How to build a cross-platform graphical user interface with Python — Russell Keith-Magee](https://i.ytimg.com/vi/nbJrfXkotq0/mqdefault.jpg)
![From Code Hero to Team Leader: Learning to Let Go - Manivannan Selvaraj
[EuroPython 2026 - S3A on 2026-07-15]
🎤 *From Code Hero to Team Leader: Learning to Let Go by Manivannan Selvaraj*
🔗 https://ep2026.europython.eu/session/from-code-hero-to-team-leader-learning-to-let-go
📝 Abstract:
As engineers grow in their careers, many of us try to support our teams by writing more code, reviewing every pull request, and stepping in to fix the hardest problems. It feels helpful and responsible. Over time though, this approach can unintentionally create too much dependency on one person.
This talk explores the shift from being the person who solves everything to becoming someone who helps the whole team succeed.
Drawing from lessons learned through experience(often the hard way :)) and from colleagues and mentors along the way, I will share practical shifts that make a difference: creating clearer technical direction, improving design conversations, sharing context early, mentoring thoughtfully and building systems that reduce reliance on any single “hero.”
If you are a mid or senior engineer who is always busy but still feels that too much depends on you, this talk aims to offer useful ideas for your own journey.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: https://creativecommons.org/licenses/by-nc-sa/4.0/ From Code Hero to Team Leader: Learning to Let Go - Manivannan Selvaraj](https://i.ytimg.com/vi/oEh3c-2sHl0/mqdefault.jpg)
![Hacking Truth: Python and the Limits of Mathematics - Miguel Ángel Fernández Gutiérrez
[EuroPython 2026 - S2 on 2026-07-15]
🎤 *Hacking Truth: Python and the Limits of Mathematics by Miguel Ángel Fernández Gutiérrez*
🔗 https://ep2026.europython.eu/session/hacking-truth-python-and-the-limits-of-mathematics
🛠️ Resources: https://go.mianfg.me/ep26
📝 Abstract:
Are mathematics a reliable way to explain reality? Can we trust them? And more importantly: what role could Python play in such profound questions?
Gödel’s Incompleteness Theorems are pillars of mathematics and computer science, revealing inherent limits in our ability to formalize truth and reason about the world. Their implications reach far beyond logic, touching philosophy, the foundations of computing, and the limits of machine reasoning. Despite their importance, understanding _why_ these results hold can feel inaccessible and abstract.
In this talk, we tackle that difficulty directly. Python will be used not only as a programming language, but as a conceptual tool to understand Gödel’s First Incompleteness Theorem through algorithmic thinking.
We will see how computational ideas make abstract concepts tangible, exploring the intellectual journey from Hilbert’s dream of a complete mathematics to the breakthroughs of Gödel, Church, and Turing. Through this lens, Python helps illuminate the boundaries of logic and computation, offering a new perspective on how mathematics works... and where its limits lie.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License: https://creativecommons.org/licenses/by-nc-sa/4.0/ Hacking Truth: Python and the Limits of Mathematics - Miguel Ángel Fernández Gutiérrez](https://i.ytimg.com/vi/oWsqoKkP_sw/mqdefault.jpg)