BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//DWBGJ9
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-DWBGJ9@programme.europython.eu
DTSTART;TZID=CET:20260715T104500
DTEND;TZID=CET:20260715T113000
DESCRIPTION:The upcoming Python 3.15 keeps improving error messages\, which
  will be the fourth out of the last five releases to establish this most r
 ecent tradition. Good errors help developers debug faster and keep beginne
 rs from giving up in frustration\n\nIn this talk we go all the way back to
  2008 and explore how error messages evolved from Python 3.0 to today. Alo
 ng the way we will also go into what makes up a good error message and why
  they are often so hard to get right. We'll also touch on how academia and
  research let us down and why good errors remain an art more than an exact
  science. I will also talk about my personal experience and the ~~bad~~ _u
 nfortunate_ error message I encountered during my first teaching job that 
 fueled my passion for compiler and language development.\n\nFinally\, I wi
 ll also argue why you not only don't have to be a compiler engineer to con
 tribute to python errors but why not being one might be an actual advantag
 e.\n\nBy the end\, you will have learned what makes a good error message\,
  how to spot a bad one and how to fix them.
DTSTAMP:20260524T130833Z
LOCATION:Theatre Hall (S2)
SUMMARY:How CPythons Errors keep getting better - Florian Freitag
URL:https://programme.europython.eu/europython-2026/talk/DWBGJ9/
END:VEVENT
END:VCALENDAR