# An announcement from the Steering Council regarding the JIT project

**URL:** <https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638>\
**Category:** Core Development\
**Tags:** steering-council\
**Created:** [June 5, 2026, 12:56pm UTC](https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638 "2026-06-05T12:56:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![thomas](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/thomas/32/5492_2.png) [@thomas](https://discuss.python.org/u/thomas)\
**Post date:** [June 5, 2026, 1:53pm UTC](https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638/4 "2026-06-05T13:53:56Z")

</div>

I’m not sure what background you’re looking for. Yes, there’s background, because the SC has been talking about this for a while. There’s been work trying to get the JIT to play nice with instrumentation, debugging, and profiling. There’s also external JITs (like CinderX), JIT-adjacent things (like Numba and PyTorch’s compile), and discussions about a tier 3 JIT. There hasn’t been a single triggering event for this request for a discussion and PEP around the JIT, if that’s what you mean. The timing is because we wanted to be clear that we’re okay with the status quo for 3.15, so we were waiting until after the beta cutoff.

---

_[View the full topic](https://discuss.python.org/t/an-announcement-from-the-steering-council-regarding-the-jit-project/107638)._