BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//KYXL
 TA
BEGIN:VTIMEZONE
TZID:Poland
BEGIN:DAYLIGHT
DTSTART:20250715T000000
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:Exploring Python Inspect: Enriching Stack Traces and Testing the U
 ntestable - Mika Allert
DTSTART;TZID=Poland:20260715T114000
DTEND;TZID=Poland:20260715T121000
DTSTAMP:20260823T012514Z
UID:pretalx-europython-2026-NHDPCM@programme.europython.eu
DESCRIPTION:If your stack traces are missing crucial information about the
  runtime state of your program(s) or if you are developing tests which ass
 ert beyond the possibilities of common testing frameworks\, then Python's 
 `inspect` module can help you out. The `inspect` standard library puts the
  power to analyze the current execution context at your fingertips. For in
 stance\, you can supercharge your stack traces by enriching them with rele
 vant variable values from any level of the call stack\, saving you valuabl
 e time trying to debug and reproduce critical issues. In addition\, `inspe
 ct` makes it easy to perform complex assertions about the execution of you
 r code\, such as from where a function is being called\, whether a nested 
 function behaves correctly\, and what signature and context generated func
 tions have.
LOCATION:S3B
URL:https://programme.europython.eu/europython-2026/talk/NHDPCM/
END:VEVENT
END:VCALENDAR