# 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:** 57

<div class="post-metadata">

**Author:** ![savannahostrowski](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/savannahostrowski/32/25496_2.png) [@savannahostrowski](https://discuss.python.org/u/savannahostrowski)\
**Post date:** [October 19, 2026, 8:35pm UTC](https://discuss.python.org/t/pep-836-jit-go-brrr-the-path-to-a-supported-jit-compiler-for-cpython/108010/57 "2026-10-19T20:35:34Z")

</div>

After further discussion, we have decided to withdraw PEP 836. The Steering Council rightly sets a high bar for a proposal of this scope, and we don’t feel we have the personal bandwidth to carry the current version forward. We continue to believe in the technical direction outlined in the PEP, including free-threaded support and a method-based frontend, and remain optimistic about the JIT’s potential in CPython. 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)._