# 2026-08-13 Python Steering Council meeting summary **URL:** \ **Category:** Committers\ **Created:** [September 7, 2026, 1:14am UTC](https://discuss.python.org/t/2026-08-13-python-steering-council-meeting-summary/108915 "2026-09-07T01:14:43Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![pablogsal](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pablogsal/32/32246_2.png) [@pablogsal](https://discuss.python.org/u/pablogsal)\ **Post date:** [September 7, 2026, 1:14am UTC](https://discuss.python.org/t/2026-08-13-python-steering-council-meeting-summary/108915/1 "2026-09-07T01:14:43Z")
- 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 from` PEP. - 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)](https://peps.python.org/pep-0836/) 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/360), [https://github.com/python/steering-council/issues/361](https://github.com/python/steering-council/issues/361))