BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pycon-sweden-2026//talk//WR7JGZ
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
BEGIN:STANDARD
DTSTART:20251119T000000
TZNAME:CET
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T030000
RDATE:20270328T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261025T030000
RDATE:20271031T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Synchronicity - how to ship both sync and async APIs - Elias Freid
 er
DTSTART;TZID=Europe/Stockholm:20261119T133000
DTEND;TZID=Europe/Stockholm:20261119T140000
DTSTAMP:20261111T055834Z
UID:pretalx-pycon-sweden-2026-WR7JGZ@pretalx.com
DESCRIPTION:Authors of many Python packages\, in particular those that per
 form network operations\, want to write async Python for the convenient an
 d performant concurrency model it provides.\n\nFor your *users'* benefit y
 ou may still want to ship both sync and async variants of your API. \nIn t
 his talk\, we walk through some strategies we've developed at Modal for ho
 w to manage release of such dual APIs\, including:\n\n- Automating API tra
 nslation using the `synchronicity` open source package\n- Managing a dedic
 ated event loop\n- An opinionated `.aio()` async API syntax\n- Advanced us
 age of the Python type system to make all of this type safe\n- Speculation
  on the future: codegen or ai-gen in the release process?
LOCATION:Auditorium
URL:https://pretalx.com/pycon-sweden-2026/talk/WR7JGZ/
END:VEVENT
END:VCALENDAR