BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//euroscipy-2026//speaker//KXUG9A
BEGIN:VTIMEZONE
TZID:Poland
BEGIN:DAYLIGHT
DTSTART:20250721T000000
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:What Is Your Simulation Doing Right Now? - Łukasz Langa
DTSTART;TZID=Poland:20260721T101000
DTEND;TZID=Poland:20260721T111000
DTSTAMP:20260908T064523Z
UID:pretalx-euroscipy-2026-C7BCMN@pretalx.com
DESCRIPTION:Your simulation is 40 hours into a 48-hour SLURM allocation an
 d it has stopped making progress. You can't restart it\, and you didn't in
 strument it. Until recently\, Python's official answer was "you should hav
 e 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 li
 brary that attaches to a running process with virtually zero overhead and 
 can tell you -- among other things -- which thread is hogging the GIL\, at
  up to a million samples per second.\n\nBut scientific Python is observabi
 lity's hardest case: long-running\, thread-heavy\, mostly native code unde
 rneath\, and increasingly on the GPU. I'll demo what the new tools do on l
 ive processes\, but will also be honest about where they still go dark tod
 ay -- native frames\, free-threaded builds\, GPU timelines -- and lay out 
 a plan for Python 3.16\, which you can help shape as well.
LOCATION:Room 1.38 (Ground Floor\, Turing)
URL:https://pretalx.com/euroscipy-2026/talk/C7BCMN/
END:VEVENT
END:VCALENDAR