Steering Council Panel
summary
Five-person Steering Council meets weekly for 90 minutes, pronounces on PEPs, enforces the Code of Conduct, and decides funding for core-dev sprints and paid roles; the developers in residence team scales from one to three and proves productive, and the security hire wins CNA control for CPython to triage and score vulnerabilities. New governance bodies (PEP 732 docs board, PEP 731 C API group, PEP 729 Typing Council) preapprove PEPs. Python 3.13 ships beta1 with removed PEP 594 modules, typing tweaks, a color multiline REPL demoed successfully, an experimental JIT with near-zero slowdown, and --disable-gil build option implementing PEP 703 in phased testing.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:34Governance and operations
- 7:18Funding and staffing
- 12:42Councils and working groups
- 19:33Python 3.13 updates
- 24:57JIT compiler and demo
- 27:36Removing the GIL
related talks
30mPython Steering Council
01h 00mKEYNOTE / Python Steering Council
21mKeynote Speaker – Python Steering Council
42mKeynote - Steering Council Panel
17mHow Python Evolves: The Role of Python Enhancement Proposals (PEPs)
54mCore Python Devs on how COVID has changed core Python development
35mInterview
26mWhat does PEP 517 mean for packaging
