BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//euroscipy-2026//speaker//KXUG9A
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-euroscipy-2026-C7BCMN@pretalx.com
DTSTART;TZID=CET:20260721T101000
DTEND;TZID=CET:20260721T111000
DESCRIPTION:Your simulation is 40 hours into a 48-hour SLURM allocation and
  it has stopped making progress. You can't restart it\, and you didn't ins
 trument it. Until recently\, Python's official answer was "you should have
  thought about that earlier." That answer has changed.\n\nPython 3.14 and 
 3.15 quietly shipped the biggest upgrade to observability in the language'
 s history: a safe\, supported way to attach a debugger to any live Python 
 process (`pdb -p`)\, and Tachyon\, a sampling profiler in the standard lib
 rary that attaches to a running process with virtually zero overhead and c
 an tell you -- among other things -- which thread is hogging the GIL\, at 
 up to a million samples per second.\n\nBut scientific Python is observabil
 ity's hardest case: long-running\, thread-heavy\, mostly native code under
 neath\, and increasingly on the GPU. I'll demo what the new tools do on li
 ve processes\, but will also be honest about where they still go dark toda
 y -- native frames\, free-threaded builds\, GPU timelines -- and lay out a
  plan for Python 3.16\, which you can help shape as well.
DTSTAMP:20260625T001031Z
LOCATION:Room 1.38 (Ground Floor\, Turing)
SUMMARY:What Is Your Simulation Doing Right Now? - Łukasz Langa
URL:https://pretalx.com/euroscipy-2026/talk/C7BCMN/
END:VEVENT
END:VCALENDAR