BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//SKGET
 8
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-ARRMQR@programme.europython.eu
DTSTART;TZID=CET:20260717T110500
DTEND;TZID=CET:20260717T113500
DESCRIPTION:Most Pythonistas handle Python objects every day\, but sometime
 s\, the bugs and performance surprises we encounter happen because we misu
 nderstand how Python actually manages memory. \nVariables are not just con
 tainers(which I previously thought)\, objects are not copied by default\, 
 and references behave differently than what many developers expect — esp
 ecially as the codebases we work with grow.\nIn this talk\, we will build 
 an accurate mental model of how Python handles objects\, references\, and 
 memory at runtime\; we will look at what really happens when objects are c
 reated\, passed to functions\, mutated\, and destroyed. \nWe will also loo
 k at how reference counting works at a high level\, why mutability matters
 \, and how these fundamental concepts come up when we examine debugging an
 d performance in our Python code.\nAfter this session\, developers will be
  more confident about their understanding of Python behaviour\, avoid comm
 on pitfalls\, and better understand what the profilers and debuggers are r
 eally saying.
DTSTAMP:20260524T121903Z
LOCATION:Auditorium Hall (S1)
SUMMARY:Pointers\, Objects\, and References - How Python Manages Memory - A
 bigail Afi Gbadago
URL:https://programme.europython.eu/europython-2026/talk/ARRMQR/
END:VEVENT
END:VCALENDAR