BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//XF7NU
 C
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-europython-2026-ENK9EF@programme.europython.eu
DTSTART;TZID=CET:20260715T143000
DTEND;TZID=CET:20260715T150000
DESCRIPTION:Most developers interact with the CPython interpreter by writin
 g code in the Python language and executing it with the bytecode interpret
 er. However\, any native extensions and any code that runs alongside or em
 beds the interpreter needs to communicate with CPython via the CPython C A
 PI. This API corresponds to an application binary interface (ABI) that nat
 ive code written in C\, C++\, Rust\, Zig\, or any other low-level programm
 ing language needs to use to directly interact with the CPython interprete
 r runtime. Understanding the ABI allows Python developers to make informed
  trade-offs when they distribute or depend on packages that contain native
  extensions.\n\nIn this talk\, I will explain what the CPython ABI is\, ho
 w it differs from the CPython C API\, and how it determines whether a pack
 age from PyPI is installable with a given installation of CPython. I will 
 discuss how CPython's stable ABI and limited C API enable substantially re
 duced distribution overhead at the cost of some performance overhead. I'll
  show how maintainers of projects that distribute compiled code in binary 
 wheels can choose to ship wheels using the stable ABI to trade off peak pe
 rformance with ease of distribution and support for new platforms.\n\nI'll
  finish by explaining how the ABI is evolving to enable improvements like 
 the free-threaded interpreter. I will share real-world experience of intro
 ducing the new free-threaded ABI to the community with the perspective ava
 ilable to a maintainer of open source projects that are core components of
  the Python ecosystem.\n\nPython 3.15 will enable a new stable ABI that al
 lows distributing one extension per platform for any interpreter newer tha
 n Python 3.15. I'll describe work done by myself and others in the communi
 ty to enable end-to-end testing of the next-generation stable ABI.
DTSTAMP:20260524T121959Z
LOCATION:Auditorium Hall (S1)
SUMMARY:What every Python developer should know about the CPython ABI - Nat
 han Goldbaum
URL:https://programme.europython.eu/europython-2026/talk/ENK9EF/
END:VEVENT
END:VCALENDAR