2025 PSC Meeting Summaries

Committers
1

The 2026 Python Steering Council has decided to publish updates on the DPO Committers category to improve transparency. (link)
The SC also decided to publish the full 2025 PSC meeting summaries for those who are not active on the Discord server.

Finally, we would like to thank @emily and @gpshead for their service as members of the 2025 Python Steering Council.

Warm regards from very cold Seoul,
Donghee
on behalf of the Python Steering Council

=========================================

2025-03-27 PSC Meeting Summary

  • Started to discuss in depth PEP 749. We have some pending questions for the typing council but we are not done yet.
  • Started to discuss in depth what is needed to move to phase 2 of free threaded Python, communication around it, problems and challenges and how to identify as many problems early as possible. (We are trying to prioritize unblocking stuff)
  • We have a bunch of pending notices that will get done soon (like the comments on PEP 750)

2025-04-03 PSC Meeting Summary

  • The remaining items for PEP 749 (Implementing PEP 649). We have finalized our questions for the Typing Council and will send these once we get a final signoff from all SC members.
  • The list of “nitpicks” for PEP 750 (Template Strings), which will also be sent pending final approval.
  • A check-in on outstanding PEPs and issues that should land for 3.14, namely PEP 773 (A Python Installation Manager for Windows).
  • Planning for the Language Summit and gathering feedback from the community on free-threading

2025-04-17 PSC Meeting Summary

2025-04-24 PSC Meeting Summary

  • We were joined in Office Hours by Brandt Bucher and Savannah Ostrowski to discuss PEP 744 (JIT Compilation) and the general plans for the JIT in Python 3.14 and beyond. I’ll leave it to them to summarize that discussion and action items, but from the SC’s perspective, we found it incredibly useful and productive, so we want to thank them for joining us.
  • After Office Hours, the SC discussed PEP 784 - Zstandard to the standard library. We’re gathering some additional information before we can make a pronouncement.
  • We discussed PEP 773, which we still plan on officially accepting tomorrow (2025-04-25)
  • We discussed Petr’s request to remove a couple of C API functions related to recursion limits, without a deprecation period. This was unanimously recommended by the C API WG, and the SC has agreed.
  • We discussed a response from Jelle to our initial feedback on PEP 749. We ran out of time so we’ll complete our response asynchronously.
  • We had some additional discussions regarding future OH topics.
  • We briefly discussed the SC panel session slated for Pycon.

2025-05-01 PSC Meeting Summary

  • Synced with DiR Łukasz on several topics, including syntax highlighting in the REPL PR, PyCon US sprint preparations, and debugging ongoing CLA bot issues.
  • PEP 749: Collected final feedback from Steering Council members based on the Typing Council’s response and preparing an official reply.
  • Discussed PyCon US panel session:
    • Agreed to balance between pre-submitted and live questions.
    • Emily has prepared this year’s presentation template (Thanks, Emily!).

2025-05-08 PSC Meeting Summary

  • OH with Eric Snow: Reviewed PEP 734 in light of current PyPI usage data and discussed next steps.
  • Held a detailed discussion on the free-threading initiative.
  • Finalized planning for the PyCon SC panel session, confirming the schedule, presentation topics, and speaker format.

2025-05-15 to 2025-05-22

  • Meeting skipped during PyCon US weeks.

2025-05-29 PSC Meeting Summary

  • Synced with DiR Łukasz:
    • Discuss transition plans for the 3.13.4 macOS release, including new Apple signing keys and improvements to buildbot.
    • Review the sprint feedback at PyCon US.
  • Discussed potential adjustments to the Language Summit format, such as topic-based scheduling and better support for attendee interaction.
  • Continued discussion on PEP 779, focusing on defining stable C API requirements and identifying key extension categories for readiness.
  • PEP 734 is progressing toward acceptance, with initial discussion around module naming and import paths.

2025-06-05 PSC Meeting Summary

  • OH with Michael Droettboom: Demoed a benchmarking system for faster-cpython using bare-metal machines. Discussions are ongoing around security, infrastructure setup, and potential PSF funding.
  • Reviewed the core developer promotion process and proposed improvements, including better feedback mechanisms and follow-up mentoring.
  • Finalized the Council’s response to PEP 734.
  • Continued discussions on the requirements and expectations for PEP 779, including documentation, performance targets, and API stability.

2025-06-12 PSC Meeting Summary

  • DiR Update with DiR Łukasz:
    • Resolved multiple regressions in Python 3.13.5.
    • Discussed adding bytecode regression checks to CI.
    • Talked about forming a Release Manager team and identifying future RM candidates.
  • Finalized the response to PEP 779.
  • Reviewed the current status of PEP 734 and discussed next steps.
  • Approved Peter’s promotion: no objections.
  • Continued discussion on core dev’s promotion timelines and expectations.

2025-06-19 PSC Meeting Summary

  • Clarified C API terminology (Stable ABI / Limited C API) in the PEP 779 announcement. An update to the announcement is planned soon.
  • Reviewed and discussed PEP 782 and PEP 750.
  • Discussed the selection process for new RM.
  • Discussed about a potential memory benchmarking page (e.g., memory.python.org), similar in concept to speed.python.org.

2025-06-26 PSC Meeting Summary

  • Bi-weekly DiR Sync (with Petr as a quick guest!)
    • The Stable ABI for Free Threading has been opened as an issue to C API WG. Will meet during office hours next week to discuss more thoroughly
    • Łukasz has been helping with memory.python.org
    • Łukasz and Deb informed the SC of a conduct report that is being handled by the PSF
  • Finalized clarifications to the SC’s PEP 779 response, which can be seen here

2025-07-03 PSC Meeting Summary

  • Office Hours with Petr Viktorin: reviewed the overarching ideas from the C API WG regarding the Stable ABI for Free Threading and Petr’s proposal, PEP 793
  • Discussed the early success of memory.python.org and next steps for moving performance benchmarks to the new site, which would eventually become benchmarks.python.org
  • Discussed ways to help the community remove blockers or settle areas struggling to reach consensus that aren’t PEP-sized
  • Discussed plans for those attending EuroPython in a couple of weeks. Some SC members will attend and can have follow-up conversations in person.

2025-07-10 PSC Meeting Summary

  • Reviewed recent core dev promotion feedback form responses and shared relevant feedback with mentors
  • Discussed type checking and type annotations in the CPython repo; SC will draft a “state of the world” for current use of annotations in the stdlib
  • Discussed PEP 782 (Add PyBytesWriter C API); SC will continue to discuss and research
  • Discussed PEP 728 (TypedDict with Typed Extra Items); Typing Council approves, SC to review
  • Discussed the state of the profiler modules in the stdlib. With the new sampling profiler coming, should we do a mini-reorg to create a stdlib package? Should profile.py be deprecated? It’s very old and extremely slow, but it does handle multiple threads.
  • Discussed RM selection for 3.16 & 3.17. SC to contact the previous RMs for feedback.

2025-07-17 PSC Meeting Summary

  • Only 3/5 attendance due to EuroPython; no decisions to be made until everyone returns
  • Continued discussion on PEPs 728, 782, 545, 793
  • Continued discussion regarding RM for 3.16 & 3.17
  • Discussed problem with concurrent.futures.InterpreterPoolExecutor in 3.14 and whether it should be a blocker or just marked as experimental and fixed in 3.15; likely an RM decision

2025-07-24 PSC Meeting Summary

  • DiR Update with Łukasz
    • Removed the curses dependency from pyrepl, improving compatibility for Emscripten/Pyodide and FreeBSD.
    • Managed the 3.14.0rc1 Windows release with minimal infrastructure support.
    • Unblocked iOS wheels after CFFI fixes (callbacks still unsupported on iOS).
    • Continued progress toward enabling mobile Python apps.
    • Discussed a potential JavaScript FFI PEP to unify approaches between Pyodide and MicroPython.
  • Deb Sync
    • Reminder to book travel early for the September Python Core Sprint (especially for PSF-funded participants).
    • Suggested a finance review meeting with Phyllis.
  • PEP Discussions
    • Discussed feedback for PEP 728.
  • Release Manager
    • SC agreed with RMs that Savannah is a good choice as Release Manager for 3.16 & 3.17.
    • Hugo to announce the decision.

2025-07-31 PSC Meeting Summary

2025-08-07 PSC Meeting Summary

  • DiR Update with Łukasz
    • cffi updated for free-threading and iOS support; version 2.0 coming soon.
    • Emscripten buildbots are green (with many test skips).
    • Released Python 3.13.6.
    • Working on editing a new podcast episode.
  • PEP Discussions
    • Sent feedback for PEP 728; awaiting a response from the Typing Council.
    • Delegated decision for PEP 694 to Dustin.
  • Other
    • Discussed how to handle community confusion about experimental projects, particularly after PEP 779 approval.

2025-08-14 PSC Meeting Summary

4 of 5 SC members met and discussed:

  • PEP 728 – TypedDict with Typed Extra Items
    • A reasonable response was received from the PEP author and its sponsor, resulting in a small PR to address previous discussions and improve the “How to Teach This” section.
    • With this update, the SC approves PEP 728 after confirming with the missing SC member
    • As a general note, the SC would like to encourage improvements to the online documentation, especially in areas of growing complexity such as typing
  • PEP 793 – PyModExport: A new entry point for C extension modules
    • The SC would like an explicit decision from the C API WG before proceeding
  • Annual Report
    • Emily met with Deb and Phyllis from the PSF to review the current budget. The Core Dev budget is healthy and has extended support for the 3 current developers-in-residence.
    • There is an outstanding item on the balance sheet that must be reconciled by the PSF before a full report can be published.
    • We discussed ensuring that we have tracking for all budget expenditures and how best to break down our “buckets” for reporting purposes.
  • Mentorship Resources
    • Emily is working with Tania and Diego to support Tania’s mentorship presentation at the upcoming Core Sprint. Information on our current areas that we want to approve along with past materials on workshops and surveys will be provided.

2025-08-21 PSC Meeting Summary

The SC met and discussed:

2025-08-28 PSC Meeting Summary

4 of 5 SC members met and discussed:

  • Funding Transifex paid service for the docs translation team. The PSC is in favor of a one-year approval without commitment to ongoing funding. The PSC encourages translators to come up with an exit strategy if future costs get untenable. We recommend the documentation team check in with the PSF every year to see if the funding still makes sense.
  • This sparked a larger discussion about the use of CPython development funds and the authority of the PSC to make decisions about how it should be spent.
  • The PSC will present some slides at the September core sprint.

2025-09-04 PSC Meeting Summary

The SC met and discussed:

  • PSF Update with Deb
    • Deb suggested regular syncs between the PSF Board and PSC, 3-4 times per year. Some board members don’t know what the PSC does, and there are areas where responsibilities intersect. The idea is to start with general topics and then drill down as necessary.
    • No DiR meeting this week
  • PEPs
    • PEP 782 – Add PyBytesWriter C API
      • Draft a PEP acceptance response, and respond to a ping email from Victor.
    • PEP 772 – Packaging Council governance process
      • Board has signed off and the pypa-committers vote is open.
    • PEP 765 – Disallow return/break/continue that exit a finally block
      • If it’s to be reverted for 3.14, it must happen before 3.14.0 and the PSC would require at least one RC with the revert. RC 3 is currently scheduled for 9/12. Pablo will send a message “it’s now or never”. The PSC strongly encourages proponents of reverting the PEP to file an blocking issue with CPython and an issue on the PSC tracker. Both the PSC and the 3.14 RM must approve.
    • Other
      • Put together UK sprint slides from the PSC.
        The PSC approves one year of Transifex paid service. Approval email was sent and it’s up to the PSF to take it from here. Any decisions about renewals are deferred to the future.
      • Discussed the creation of an “observability” working group, similar to the C API WG, which would coordinate future development of debugging and performance APIs.
      • Check-in with Ee to make sure we’re on track for Bloc STAR voting for the next PSC election.

2025-09-11 PSC Meeting Summary

  • 3 of 5 SC members had a brief meeting and discussed the SC presentation at the Core Sprint and pending PEP responses.

2025-09-18 PSC Meeting Summary

  • The SC did not have an official meeting, as 3 of 5 members were in-person at the Core Sprint. We met ad hoc to address potential release blockers/reversions. It was decided not to revert any changes; see the full statement here.

2025-09-25 PSC Meeting Summary

  • The SC had office hours with Tal Einat to discuss updates to the deferred PEP 661 (Sentinel values)
    • Current state: Registry idea dropped; using standard pickling/unpickling. Reference implementation to be updated.
    • Main open issue: Truthiness/boolean behavior — some want configurability, but most favor simplicity. This is been a surprisingly contentious topic!
    • Discussion Consensus:
      • Keep sentinels always truthy (matches standard library usage).
      • Avoid making bool configurable or allowing subclassing.
      • Simpler design preferred.
      • Reference in Python for now; final version to be in C if accepted.
    • The SC met and discussed:
      • Publishing SC Minutes and Summaries
        • Discussed making summaries more public, as the current summaries on Discord updates are well-received but not widely shared.
        • Discussed if we could we easily expose a public agenda in Notion.
      • PEP 793 – (PyModExport: A new entry point for C extension modules)
        • The C API WG has posted a response: 4 for, 1 against, 1 abstain.
        • Discussion Consensus:
          • We don’t want to hold up work. Our goal: ensure this is going in the right direction.
          • We request gathering broader input (bindings, pydantic, other core devs) - contacted Petr to gather more feedback.
      • Voting provider for the upcoming SC election in November/December
        • We have been in touch with Ee. The provider looks good; one non-critical missing feature expected to be ready before the election.
      • Core Sprint Hosting
        • Discussed possibly formalizing host selection via an RFP.
        • Pondering if we want a more deliberate rotation between cities.

2025-10-02 PSC Meeting Summary

2025-10-09 PSC Meeting Summary

  • The SC met and discussed:
    • Learnings and possible improvements to the PEP process based on the PEP 765 ”return in finally” decision and post-announcement discussion.
    • PEP 791 “intmath” and decided that math.integer would be the name. With that, the PEP was accepted, with notification to be drafted.
    • Regarding alternating sprints between PyCon US and EuroPython, we decided to draft a non-binding vote to gauge the temperature on DPO.
    • Still awaiting responses to PSC feedback on PEP 793 “PyModExport”.
    • Decided on dates for upcoming 2026 term PSC elections, with email to Ee requesting PEP 8107 drafting and election administration.
    • Mark the request to elevate Raspberry PI ARM64 to Tier 3 as approved.

2025-10-16 PSC Meeting Summary

  • The SC had a sync meeting with DiR.
    • Shared updates on the editing progress regarding core.py during the Cambridge Core Sprint.
    • Shared the preparation for removing Python 3.9 from buildbots.
    • Talked about Python 3.14 release.
  • The SC also discussed our response to PEP 765 (Disallow return/break/continue that exit a finally block).

2025-10-23 PSC Meeting Summary

2025-10-30 PSC Meeting Summary

  • The SC met with the DiR, Łukasz, and discussed:
    • The last ever 3.9! 3.9.25 will be released shortly, covering a few minor issues (no major security issues).
    • Re-writing speed.python.org
    • Brief planning and logistic questions around future conferences and locations related to core sprint plans
  • The SC also discussed:
    • PEP 798 (Unpacking in Comprehensions)
      • We received feedback from the community and did some internal polls with colleagues
      • Overall, we are positive on the PEP but want to ensure that the waters are not muddied with yield from
      • Decided to accept the PEP without yield from, and will release an acceptance statement
    • PEP 810 (Explicit lazy imports)
      • Discussed and landed on lazy for the keyword after entertaining multiple options
      • Decided to accept the PEP, and will release an acceptance statement
        Brief discussion on possible improvements to the PEP process, more to come!

2025-11-06 PSC Meeting Summary

  • The SC held office hours with Emma Smith.
    • The main discussion focused on ways to ensure that DPO discussions stay on track, respectful, and productive, and how the SC can step in early to settle sub-topics and questions, avoiding long, difficult to follow threads.
    • SC also discussed several possible action items, such as encouraging PEP authors to start new threads at key milestone changes and providing early feedback from the SC, among others.
  • The SC met and discussed:
    • SC decided to remove commit privileges from inactive core developers.
    • The decision was made with security concerns in mind, and the SC noted that commit access can be restored at any time upon request.
    • SC also finalized the summary and publication of the meeting notes.

2025-11-20 PSC Meeting Summary

  • The SC held office hours with Petr Viktorin to discuss various details around CPython development.
  • Continued to have discussions about benchmarking hardware, the budget, and where to house the machines

2025-12-04 PSC Meeting Summary

  • Chatted about election in progress, upcoming hand-off stuff.
  • Discussed if docs translations make sense in the GitHub python org. sc#322
  • Discussed the creation of a Platforms/ dir in the cpython repo and what should move in and when. sc#317
  • Discussed two WASI questions from Brett Cannon:
    • The Platforms/ dir and what to put in it sc#317
    • How to declare WASI support in PEP 11 sc#319
  • Discussed Petr’s “friendlier unsupported platforms” PEP11 sc#324
  • Discussed the PSRT definition PEP 811 from Seth - accepted!
  • Discussed the Language Summit 2026 location.
  • We want it to support moving it to EuroPython for 2026, but caveats still in flight are: locale and venue are still not defined.
    • Requirements we haven’t codified and thus communicated directly to EuPy folks yet have themes of:
    • We’re holding up PyCon US planning with the unknown, global international travel friendly locale needs
      • Lead time for travel Visas
      • PSF grant funding expense requirements
    • So TBD w/:crossed_fingers: - goal know for sure by late Dec/early Jan.
    • It’d be a shame to need to make 2027 be the first alternating year.
    • Emily, Hugo, & Lukasz in contact with Ege & EU folks.
  • Discussed some Azure credits sent Python’s way from Ezio
    • Passed those on to Ee and Lukasz to consider.

2025-12-11 PSC Meeting Summary

  • Synced up with Developer in Residence Łukasz & PSF executive director Deb.
    • Discussed macOS releases on GHA, buildbot flakiness, pyrepl “security” report.
    • PSF staff, DiRs, core dev funding discussions
    • Checked in on 2026 Language Summit decision
      • Venue not quite settled
      • We have timelines for travel grants & visas, etc.
      • Conversations in progress. Should have EuroPy details very soon.
    • Office hours with Filipe (yay office hours in use, welcome!)
    • Election ends in a couple days, next week: a handoff meeting

2025-12-18 PSC Meeting Summary

  • The 2025 and 2026 SCs met and discussed handoff procedures, outstanding issues, and general knowledge transfer. The 2026 SC will reconvene in January.
14 Likes
2

Some of the formats are broken while copying and pasting from Discord.
I am fixing them. (Done)

1 Like