# 2026-07-02 Python Steering Council meeting summary **URL:** \ **Category:** Committers\ **Created:** [August 5, 2026, 4:27pm UTC](https://discuss.python.org/t/2026-07-02-python-steering-council-meeting-summary/108421 "2026-08-05T16:27:26Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![barry](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/barry/32/42_2.png) [@barry](https://discuss.python.org/u/barry)\ **Post date:** [August 5, 2026, 4:27pm UTC](https://discuss.python.org/t/2026-07-02-python-steering-council-meeting-summary/108421/1 "2026-08-05T16:27:26Z")
We met with DiR Petr on our regular sync. - We discussed whether SC members _must_ also be on PSRT, and decided that isn’t required. - We discussed the [Debian multiarch patch](https://github.com/python/steering-council/issues/356#issuecomment-4870998618). Petr is +1 - There should be no measurable impact on startup because `importlib` only scans the directory once. - **[Decision](https://discuss.python.org/t/can-we-consider-an-unconditional-change-of-abi3t-so-to-abi3t-soabi-platform-so-for-3-15-last-minute/107919/7): search for the arch specific one first, then the bare `so`**. - We also discussed [baking IEEE floating point into the the ABI](https://github.com/capi-workgroup/decisions/issues/107), which would make building on non-IEEE floating point platforms impossible. - We do not currently have any supported platforms that are non-IEEE floating point, but there may be others out there we don’t know about. - The C API WG is fine with that. - **Decision: Keep the function failable even if no platform currently fails (doc change only)**. - We continue to discuss the JIT; the [PEP 836](https://peps.python.org/pep-0836/) authors have scheduled SC Office Hours. - There will be an SC Panel at EuroPython. All SC members except Barry will be there. - We discussed travel grant requests for EuroPython. Agenda for next meeting: - No meetings until after EuroPython.