The 2026 PSC met for the first time in the new year, and with the current members seated. We’re trying some new things in response to previous feedback, by posting our meeting summaries and coming agenda both in this category and on the #steering-council-comms channel on the Python Core Team Discord server, and sharing the summaries in a more timely manner.
Without further ado:
- This was the first meeting of the new year and with just the 2026 SC members.
- We discussed general meeting logistics, confirmed that the new time works for everyone, and had a general tour of Notion. We also had some additional housekeeping for access to GitHub repos and other resources following the transition to the 2026 SC.
- We agreed that we will prioritize PEPs for following week reading and discussion, and publish our planned agenda for visibility.
- We agreed to publishing on the DPO Committers category for better transparency. This category can be read by anyone and commented on by the Core Team. We are looking into automatically mirroring that to the private
#steering-council-commschannel on the Core Team Discord (for now, we’ll mirror manually). - We plan on publishing a 2025 PSC wrap-up summary to the Inquisition category on DPO.
- We will share the updated SC Office Hours schedule and sign-up calendar. (Done here).
- We closed a carry-over topic from 2025 regarding free-threading docs, since that has already been resolved by the FT team.
- We had a lengthy discussion about various project process issues, and plan on continuing to improve various aspects about the Python development process, including ensuring that project policies are well-understood by the Core Team.
- Our PEP agenda for next week, in rough priority order, and time permitting: