BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//YKWMBZ
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-YKWMBZ@programme.europython.eu
DTSTART;TZID=CET:20260716T120500
DTEND;TZID=CET:20260716T123500
DESCRIPTION:Your FastAPI + SQLAlchemy tests pass alone but fail together. D
 ata leaks between tests\, and cleanup becomes slower. Meanwhile\, it seems
  effortless in Django. Why?\n\nThis isn't a framework war - we'll dig into
  what Django actually does behind the scenes to keep the database clean be
 tween tests and why that approach isn’t straightforward to replicate in 
 a typical SQLAlchemy setup.\n\nWe'll explore common cleanup strategies lik
 e recreating schema\, truncating\, transaction wrapping or template databa
 ses and benchmark how they scale as your test suite grows. \n\nYou'll leav
 e with a clear understanding of why this problem exists and practical\, be
 nchmarked options to keep your test suite fast and data isolated.\n\nAimed
  at intermediate Python developers comfortable with writing tests and fami
 liar with basic database concepts like transactions.
DTSTAMP:20260524T131320Z
LOCATION:Chamber Hall B (S3B)
SUMMARY:Django’s Magic\, FastAPI’s Reality: Test Isolation at Scale - M
 aciej Sobczak
URL:https://programme.europython.eu/europython-2026/talk/YKWMBZ/
END:VEVENT
END:VCALENDAR