BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//JYJR
 AY
BEGIN:VTIMEZONE
TZID:Poland
BEGIN:DAYLIGHT
DTSTART:20250717T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251026T030000
RDATE:20261025T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T030000
RDATE:20270328T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Lazy imports and the art of interpreter procrastination - Pablo Ga
 lindo Salgado\, Noah Kim
DTSTART;TZID=Poland:20260717T135500
DTEND;TZID=Poland:20260717T142500
DTSTAMP:20260823T012515Z
UID:pretalx-europython-2026-RGBSS8@programme.europython.eu
DESCRIPTION:From CLI developers to maintainers of large applications\, man
 y Python developers have been bitten by the high overhead of eagerly loadi
 ng imports. Long start-up times can make it prohibitively costly to run si
 mple commands like --help\, and the memory overhead from loading every imp
 orted module eagerly can trigger Out-Of-Memory errors in production.\n\nAf
 ter the most discussed PEP thread in the history of discuss.python.org\, w
 ith hundreds of messages and fierce debate\, Python 3.15 finally brings Ex
 plicit Lazy Imports to the language. With a simple new keyword\, you can n
 ow defer module loading until the moment you actually need it. This is one
  of the most requested performance features in Python's history\, and fina
 lly it's here.\n\nThis presentation will take you through how we got here 
 and where we're going. We'll look at why existing workarounds never quite 
 worked\, and how an earlier proposal (PEP 690) tried to make all imports l
 azy by default but was rejected. Then PEP 810 emerged with a different app
 roach: explicit\, opt-in syntax that the community accepted.\n\nThe heart 
 of this talk is discovering how lazy imports actually work inside the inte
 rpreter. 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 abou
 t the future tooling that we are baking that will help you adopt this safe
 ly 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 
 to understand what's happening under the hood\, this talk will give you ev
 erything you need to start using lazy imports with confidence.
LOCATION:S1
URL:https://programme.europython.eu/europython-2026/talk/RGBSS8/
END:VEVENT
END:VCALENDAR
