BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//ZFJEUJ
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-ZFJEUJ@programme.europython.eu
DTSTART;TZID=CET:20260717T143500
DTEND;TZID=CET:20260717T150500
DESCRIPTION:Pandas now natively supports PyArrow-backed data types. But wha
 t does that actually mean? If you've ever wondered how these two libraries
  relate to each other\, whether they compete or complement each other\, an
 d what happens to your data when it moves between them\, this talk is for 
 you.\n\nAs PyArrow maintainers\, we took on the challenge of digging into 
 the conversion code between PyArrow and Pandas\, and we're here to share w
 hat we've learned. We'll show you what's really going on under the hood: h
 ow Arrow's columnar format differs from Pandas' block-based memory layout 
 (including what a BlockManager actually is)\, when data can be shared with
 out copying\, and when a full copy is unavoidable.\n\nWe'll also clarify w
 hat each library is designed for and how they work together rather than ag
 ainst each other. With pandas increasingly adopting PyArrow as a backend\,
  understanding this relationship is becoming essential rather than optiona
 l.\n\nThis talk is aimed at Python developers and data engineers who want 
 to deepen their understanding of what's happening beneath the surface.
DTSTAMP:20260524T130740Z
LOCATION:Chamber Hall A (S3A)
SUMMARY:Stop Guessing\, Start Understanding: How Arrow and Pandas Exchange 
 Data - Alenka Frim\, Raúl Cumplido Domínguez
URL:https://programme.europython.eu/europython-2026/talk/ZFJEUJ/
END:VEVENT
END:VCALENDAR