BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//FWGLE
 3
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-FBQQXS@programme.europython.eu
DTSTART;TZID=CET:20260717T110500
DTEND;TZID=CET:20260717T113500
DESCRIPTION:Do you maintain a Python library\, REST API or any other user-f
 acing interface? Breaking changes are frowned upon\, but from a a certain 
 project size\, they become unavoidable.\n\nHow do you make the breaking ch
 anges manageable? How should you version your package / API? Should you pu
 t an upper bound on your dependencies?\n\nWe'll discuss deprecation\, forw
 ard and backward compatibility\, upgrade strategies and more\, illustrated
  on real-world examples. Our main focus will be on API changes of Python l
 ibraries\, but the principles are widely applicable.
DTSTAMP:20260524T121632Z
LOCATION:Chamber Hall A (S3A)
SUMMARY:Breaking changes – not great\, not terrible - Jan Musílek
URL:https://programme.europython.eu/europython-2026/talk/FBQQXS/
END:VEVENT
END:VCALENDAR