- The Steering Council had its regular check-in with Petr (Developer-in-Residence) and discussed several topics including two ideas he is exploring, one of which may become a PEP, including a proposal to expose type object details through an API; the security issue review process; and his feedback on the async
yield fromPEP. - The SC discussed logistics for the upcoming Core Developer Sprint.
- The SC continued discussing PEP 836 (JIT Go Brrr: The Path to a Supported JIT Compiler for CPython) after an office hour session with the authors, focusing on what the PEP is asking for in the near term (resuming JIT work in
main), how its compatibility and stability claims should be stated, whether semantic changes would need a separate PEP, the proposed timeline, and a regular check-in cadence with the SC. - The SC will follow up with the PEP authors on whether the PEP answers the questions we asked in our request for a PEP.
Agenda for next week:
- Finish the JIT discussion
- PSRT follow-up (PEP 811)
- Two requests to amend PEP 11: Tier 3 support for riscv64, and dropping the buildbot requirement for platforms covered by CI (https://github.com/python/steering-council/issues/360, https://github.com/python/steering-council/issues/361)