BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//Y8QAUA
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-Y8QAUA@programme.europython.eu
DTSTART;TZID=CET:20260715T104500
DTEND;TZID=CET:20260715T113000
DESCRIPTION:Free-threaded Python\, the effort to remove the Global Interpre
 ter 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 a
 nother Python 2 to 3 migration.\n\nThis overview will explain what free-th
 reading 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 whe
 n the GIL is disabled. And yes\, we'll show some threads go _brrr_.\n\nAlt
 hough we'll mention some complex\, deeply technical problems\, this is not
  a technical deep dive and any experience level is welcome.
DTSTAMP:20260524T130911Z
LOCATION:Auditorium Hall (S1)
SUMMARY:Free-threaded Python: past\, present and future - Thomas Wouters
URL:https://programme.europython.eu/europython-2026/talk/Y8QAUA/
END:VEVENT
END:VCALENDAR