BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//H7DVRJ
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-H7DVRJ@programme.europython.eu
DTSTART;TZID=CET:20260715T160500
DTEND;TZID=CET:20260715T163500
DESCRIPTION:Say you've built a library whose main value is providing built-
 in integrations with a considerable number (say 60+) of different Python p
 ackages. That's cool\, and your users are loving the out-of-the-box experi
 ence. (Being blissfully unaware of the lengths you had to go to in the bac
 kground to make things work "seamlessly" helps.) Everything seems to be wo
 rking fine\, you get the odd bug report or feature request\, the usual.\n\
 nThen one day you wake up and your otherwise fairly chill issue tracker is
  drowning in folks experiencing an issue with your library that breaks the
 ir app. Your first thought is\, why is this coming up now\, when your last
  release was two weeks ago? And then you realize: It's not your release th
 at broke the library.\n\nAll the third party code you're integrating with?
  It's become *your* code by extension. You need to react if something chan
 ges upstream and breaks your integration in unexpected ways. You can write
  your integrations so defensively that no one will ever want to read them 
 again\, but it's not enough: you can't anticipate every single change each
  of the 60+ packages will ever make.\n\nLet's assume having your users act
  as a release monitoring system by notifying you on your issue tracker is 
 not what you want. How do you go about this? You'll want somehow to detect
  breakage early\, so you can go fix things before your users are hit by th
 em. And ideally you'd do it in a way that maintaining it is not a nightmar
 e.\n\nThis talk will take you through one such journey\, from recognizing 
 the problem\, to various attempts at making it better\, to eventually arri
 ving at a solution that's good enough for now (tm).\n\nYou might like this
  talk if you:\n- Have to deal with integrations in some shape or form\n- A
 re relying on third-party packages heavily\n- Don't like maintaining thing
 s by hand\n- Like to have that "this can be automated with a script" itch 
 scratched\n- Are intrigued that there's a talk that has the word "bananas"
  in the title
DTSTAMP:20260524T130658Z
LOCATION:Chamber Hall A (S3A)
SUMMARY:How to Maintain 60 Integrations and Not Go Bananas - Ivana Kellyer
URL:https://programme.europython.eu/europython-2026/talk/H7DVRJ/
END:VEVENT
END:VCALENDAR