BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2023//speaker//HUBV7
 F
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-2023-NVW8EF@programme.europython.eu
DTSTART;TZID=CET:20230719T121000
DTEND;TZID=CET:20230719T124000
DESCRIPTION:Updating Python versions often forces us to update native exten
 sions at the\nsame time. But what if you need to update Python because of 
 a security issue\,\nbut cannot (yet) move to a newer version of a dependen
 cy? Or you are running a\nproprietary binary extension that cannot easily 
 be recompiled?\n\nThe HPy project provides a better C extension API for Py
 thon. It compiles to\nbinaries that work across all versions of CPython\, 
 PyPy\, GraalPy. HPy makes\nporting from the existing C API easy and its de
 sign ensures that the binaries\nwe produce today stay binary compatible wi
 th future Python versions.\n\nNumPy is the single largest direct user of t
 he CPython C API we know of. After\nover 2 years of work and more than 30k
  lines of code ported\, we can demonstrate\nNumPy running its tests and be
 nchmarks with HPy. We will show the same NumPy\nbinary run on multiple CPy
 thon versions and GraalPy. And we will discuss\nperformance characteristic
 s of this port across CPython\, GraalPy\, and PyPy.
DTSTAMP:20260617T071243Z
LOCATION:PyCharm (Forum Hall)
SUMMARY:HPy: The Future of Python Native Extensions - Štěpán Šindelář
 \, Florian Angerer
URL:https://programme.europython.eu/europython-2023/talk/NVW8EF/
END:VEVENT
END:VCALENDAR