I am the maintainer of the pyperf project and pyperformance project, and I‘ve supported adding features for the Faster-CPython project and PEP-703 project aka free-threaded CPython.
I have experience supporting recent important topics of CPython, and I know what things are needed for those projects. (free-threaded / subinterpreter/ faster-cpython)
These days, I try to centralize various container files in the Python team’s single mono repository.
This year, I organized one regional CPython sprint in PyCon Korea 2025
If I am elected as the Steering Council member:
I will provide all possible support for the successful landing of the PEP 703 project at CPython 3.14 from the performance view and library compatibility issue to improve the possibility of switching the default build.
I will provide all possible support for the successful experimentation of JIT projects and supporting optimization for ARM architectures.
I will strive to gather the requirements for CPython from regions with few CPython core devs and try to become a bridge between core teams and various cultural background contributors.
I will try to make a better experience for people who participate in the US PyCon Sprint, especially for first-time contributors, with my experience organizing APAC regional CPython sprints.
My Contribution History for Regional CPython Sprint
Just wanted to take the opportunity to thank you for all your work on pyperf and pyperformance – tools that are keeping our performance work honest and data-driven.
I’m particularly grateful for the successful CPython Sprints at both PyCon APAC and PyCon Korea last year. Continuing this momentum, we also had another great sprint at PyCon Korea this year. In Korea, even though we ran these as mentored sprints, we achieved remarkable results with numerous Pull Requests and discovered many potential future contributors. These achievements are being recognized even at the government level as a successful case of open-source ecosystem development.
As an organizer of PyCon in Asia, I’ve always noticed a shortage of local contributors. While we’ve been running PyCon events with love for Python and desire to grow our community, I felt we needed more people contributing to the core project.
One challenge we face is that sprint culture is not yet established in Asia. We’re working to build it, but it takes time and effort. Currently, we’re operating in a mentored sprint format, but with continued investment and support from core developers, I believe we can eventually evolve into full-fledged sprints.
If more CPython core developers could visit our region, we would do our best to organize meaningful sprints. We’re committed to making these opportunities work, regardless of the challenges. While we may still be at the mentored sprint stage, with your investment in our region, I believe we can develop a stronger sprint culture over time.
We continue working to nurture more contributors from the Asian region. Python can truly advance when diverse regional perspectives and opinions are reflected. To support this vision, we are ready to actively welcome and support CPython sprints in the APAC region.
I collaborated with Donghee on BOLT for CPython project, and can vouch for his leadership, technical and communication skills. Thank you for making CPython faster.