BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//VX8MV
 F
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-QYVZN8@programme.europython.eu
DTSTART;TZID=CET:20260715T164500
DTEND;TZID=CET:20260715T173000
DESCRIPTION:Join us for a very special live episode of Core.py as Pablo Gal
 indo Salgado and Łukasz Langa somehow convince Guido van Rossum to sit do
 wn for what will almost certainly begin as a sensible conversation about P
 ython and quickly spiral into war stories\, controversial design decisions
 \, ancient mailing-list archaeology\, embarrassing bugs\, impossible audie
 nce questions\, and the occasional existential crisis about discuss.python
 .org. Expect behind-the-scenes stories you’ve never heard before\, plent
 y of laughs\, and a rare chance to watch three people who have collectivel
 y shaped Python try to remember why they made half of its features in the 
 first place. Buckle up: this one’s live\, unscripted\, and anything coul
 d happen.
DTSTAMP:20260711T113031Z
LOCATION:S1
SUMMARY:Core.py recording with Guido van Rossum - Pablo Galindo Salgado\, 
 Łukasz Langa\, Guido van Rossum
URL:https://programme.europython.eu/europython-2026/talk/QYVZN8/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-europython-2026-RGBSS8@programme.europython.eu
DTSTART;TZID=CET:20260717T135500
DTEND;TZID=CET:20260717T142500
DESCRIPTION:From CLI developers to maintainers of large applications\, many
  Python developers have been bitten by the high overhead of eagerly loadin
 g imports. Long start-up times can make it prohibitively costly to run sim
 ple commands like --help\, and the memory overhead from loading every impo
 rted module eagerly can trigger Out-Of-Memory errors in production.\n\nAft
 er the most discussed PEP thread in the history of discuss.python.org\, wi
 th hundreds of messages and fierce debate\, Python 3.15 finally brings Exp
 licit Lazy Imports to the language. With a simple new keyword\, you can no
 w defer module loading until the moment you actually need it. This is one 
 of the most requested performance features in Python's history\, and final
 ly it's here.\n\nThis presentation will take you through how we got here a
 nd where we're going. We'll look at why existing workarounds never quite w
 orked\, and how an earlier proposal (PEP 690) tried to make all imports la
 zy by default but was rejected. Then PEP 810 emerged with a different appr
 oach: explicit\, opt-in syntax that the community accepted.\n\nThe heart o
 f this talk is discovering how lazy imports actually work inside the inter
 preter. We'll trace through the bytecode\, see how proxy objects stand in 
 for unloaded modules\, and watch the moment when your code first touches a
  lazy import and the real module snaps into place. You'll also learn about
  the future tooling that we are baking that will help you adopt this safel
 y in your own projects.\n\nWhether you're a beginner curious about Python'
 s future\, someone looking to speed up your CLI tools\, or you just want t
 o understand what's happening under the hood\, this talk will give you eve
 rything you need to start using lazy imports with confidence.
DTSTAMP:20260711T113031Z
LOCATION:S1
SUMMARY:Lazy imports and the art of interpreter procrastination - Pablo Gal
 indo Salgado
URL:https://programme.europython.eu/europython-2026/talk/RGBSS8/
END:VEVENT
END:VCALENDAR
