# PEP 836: JIT Go Brrr: The Path to a Supported JIT Compiler for CPython

**URL:** <https://discuss.python.org/t/pep-836-jit-go-brrr-the-path-to-a-supported-jit-compiler-for-cpython/108010>\
**Category:** PEPs\
**Created:** [July 3, 2026, 4:45pm UTC](https://discuss.python.org/t/pep-836-jit-go-brrr-the-path-to-a-supported-jit-compiler-for-cpython/108010 "2026-07-03T16:45:34Z")\
**Posts on this page:** 1\
**Showing post:** 61

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [October 20, 2026, 4:33pm UTC](https://discuss.python.org/t/pep-836-jit-go-brrr-the-path-to-a-supported-jit-compiler-for-cpython/108010/61 "2026-10-20T16:33:43Z")

</div>

> [@timkofu](#):
>
> We Python users are very much looking forward to having the best possible JIT that works with free threading.
> 
> We want to extract the most possible work from the hardware we can afford, and a JIT would help with that.

Then hopefully you and others can organize yourselves to continue on with the work outside of the CPython repo.

> [@barry-scott](#):
>
> Does this mean that the JIT work is stopped?

In CPython’s repo, yes. Whether others in the community organize to keep it going is up to the community.

> [@Sacul](#):
>
> My worry is the 6 months window for the JIT to be kept in Main

The point of the PEP was to justify the JIT work staying in `main`, so the withdrawal of the PEP means it will come out and live somewhere else (“We’ll make the reference implementation available and link it from the withdrawn PEP so others who are interested can explore and build on that.”).

---

_[View the full topic](https://discuss.python.org/t/pep-836-jit-go-brrr-the-path-to-a-supported-jit-compiler-for-cpython/108010)._