BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pyconde-pydata-2026//speaker//JLP8VR
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-pyconde-pydata-2026-JJDCW3@pretalx.com
DTSTART;TZID=CET:20260414T114500
DTEND;TZID=CET:20260414T121500
DESCRIPTION:On Kubernetes\, your Python app runs in a hostile environment\,
  fighting for resources in a straitjacket\, bombarded with signals\, and b
 eing killed and ruthlessly dragged back to life time and again. This is in
  stark contrast to the wonderful weather of a Linux web server or the blis
 sful utopia of localhost. If not hardened properly\, your Python app will 
 find the burden of being containerized too hard to bear. And the result? Z
 ombies!\n\nWhether you are a Kubernetes expert\, or you just deployed your
  first containerized Hello World\, we will together explore how the Python
  Interpreter\, the Linux Kernel and Kubernetes interact with each other.\n
 \nWe will uncover why Python struggles as an init process\, how Kubernetes
  CPU-limits fight the Global Interpreter Lock (GIL) and why Python’s Gar
 bage Collector cannot save you from sudden OOM kills. Most importantly\, w
 e will see how to identify\, debug\, and avoid containerized Python pitfal
 ls. The goal of this talk is to help you stop treating your container like
  a server and learn to write Cloud-Native Python that knows exactly where 
 it lives.
DTSTAMP:20260412T141623Z
LOCATION:Titanium [2nd Floor]
SUMMARY:Python Hates Being PID 1: Writing Container-Aware Code for Kubernet
 es - Kavish Nareshchandra Dahekar
URL:https://pretalx.com/pyconde-pydata-2026/talk/JJDCW3/
END:VEVENT
END:VCALENDAR