BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//B7CMBD
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-B7CMBD@programme.europython.eu
DTSTART;TZID=CET:20260717T114500
DTEND;TZID=CET:20260717T121500
DESCRIPTION:Step 1: Fix a bug\nStep 2: ???\nStep 3: Core developer\n\nOk\, 
 it's not that simple but it's also not as mysterious as it might seem!\n\n
 About three years ago I fixed an obscure bug in the unittest module. Today
 \, I'm a core developer. This talk is about what happened in between\, and
  how you can start contributing too!\n\nOver the years\, I got to work on 
 many different areas of Python. I've fixed bugs in the parser\, added impo
 rt autocomplete to the REPL\, worked on gettext tooling\, and eventually f
 ound my way to the JIT compiler\, all things I knew little about before di
 ving in.\n\nGetting started contributing to Python can be intimidating\, s
 o I'll share some practical things I learned along the way such as:\n\n- H
 ow is the CPython project organized?\n- How do you find something to work 
 on? (and why it doesn't have to be code!)\n- What happens after you submit
  a PR?\n- How do you navigate a 30 year old codebase without getting lost?
 \n\nIf you've ever wanted to contribute to Python but weren't sure where t
 o start\, this talk is for you.
DTSTAMP:20260524T130554Z
LOCATION:Auditorium Hall (S1)
SUMMARY:Become a Python Core Developer in 3 Easy Steps - Tomas Roun
URL:https://programme.europython.eu/europython-2026/talk/B7CMBD/
END:VEVENT
END:VCALENDAR