Python Steering Council Panel
summary
A five‑person elected Steering Council explains concrete activity: funding and hiring developers in residence (sponsored roles with no sponsor control), running an annual core‑team sprint (San Francisco this year hosted by OpenAI), and launching the packaging council (PEP 772) to address packaging. Python 3.15 ships lazy imports and frozen dict plus a low‑overhead profiler; free‑threading requires broader testing before defaulting; Rust support is being prototyped for isolated modules while build and platform constraints get worked out.
AI-written summary · about
chapters (22)
- 0:00Introductions and panel setup
- 1:34Role of the Python Steering Council
- 3:00Developers in residence and funding
- 5:48Core team sprints and PSF support
- 6:11Highlights of Python 3.15 features
- 8:39Python 3.15 release schedule and contributions
- 9:42Q&A with submitted questions
- 10:29Python packaging and the Packaging Council
- 12:59Timeline for free threading adoption
- 15:07Testing and reverting changes in Python
- 16:08Criteria for evaluating PEPs
- 17:34Surprises and challenges in PEP reviews
- 19:21Consensus building in the Steering Council
- 20:49Balancing feature costs and user impact
- 21:52Working groups and C API expertise
- 22:14Future of Python versioning
- 22:59Backporting lazy imports and release policies
- 23:44Potential use of Rust in CPython
- 26:53Standard library size and Python’s future
- 29:20Evolving Python’s governance structure
- 30:22Steering Council members’ pets
- 30:43Final call to try Python 3.15 and closing remarks
related talks
32mReinventing the Wheel: A Community-Driven Roadmap for Python Packaging
01h 30mPanel: Building a Stronger Open Source Python Data Community
45mMaintainer panel
20mKEYNOTE / Python Software Foundation Community Address
41mHow to Grow an Open Source Project: A Case Study of Python
40mOops! I Became an Open Source Maintainer! 😱
01h 27mISO C++ Standards Committee Panel Discussion
38mTools for Maintaining an Open Source Project