# 2026-06-25 Python Steering Council meeting summary

**URL:** <https://discuss.python.org/t/2026-06-25-python-steering-council-meeting-summary/108415>\
**Category:** Committers\
**Created:** [August 5, 2026, 12:54pm UTC](https://discuss.python.org/t/2026-06-25-python-steering-council-meeting-summary/108415 "2026-08-05T12:54:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**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:** [August 5, 2026, 12:54pm UTC](https://discuss.python.org/t/2026-06-25-python-steering-council-meeting-summary/108415/1 "2026-08-05T12:54:33Z")

</div>

- We continued our discussion of [PEP 797 (Shared Object Proxies)](https://peps.python.org/pep-0797/) and voted to reject it. A formal rejection notice will follow.
- In response to [Update PEP 3149 to explicitly include the stable ABI · Issue #355 · python/steering-council · GitHub](https://github.com/python/steering-council/issues/355), we confirmed that we don’t retroactively update already-accepted PEPs.
- On [Deprecated `F` and `D` format in the `struct` module in Python 3.16 (use `Zf` and `Zd` instead) · Issue #352 · python/steering-council · GitHub](https://github.com/python/steering-council/issues/352), we agreed it’s fine to document the deprecation in 3.15 and add the warnings in 3.16.
- We discussed the updates to the announcement about the future of the JIT compiler and the current state of the discussion.
- We started to discuss [Request for a blameless post-mortem of the Core Sprint decision process · Issue #353 · python/steering-council · GitHub](https://github.com/python/steering-council/issues/353)

Agenda for next meeting:

- Post the [PEP 797](https://peps.python.org/pep-0797/) rejection notice.
- Send our responses on [python/steering-council#355](https://github.com/python/steering-council/issues/355) and [#352](https://github.com/python/steering-council/issues/352)
- Follow up on JIT PEP progress.
