# PEP 836: JIT Go Brrr: The Path to a Supported JIT Compiler for CPython **URL:** \ **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:** 38
**Author:** ![eric.snow](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/eric.snow/32/31_2.png) [@eric.snow](https://discuss.python.org/u/eric.snow)\ **Post date:** [July 17, 2026, 6:54am UTC](https://discuss.python.org/t/pep-836-jit-go-brrr-the-path-to-a-supported-jit-compiler-for-cpython/108010/38 "2026-07-17T06:54:04Z")
I don’t want to add noise here, but I do want to express my support for the JIT and to push back against some of the ongoing pressure. I think it’s worth having a JIT implementation in the repo and that the current JIT is worth keeping, and I agree with documenting the design and addressing concerns. However, I disagree with blocking further development in main like has been done, and with making unnecessary demands on the folks working on the JIT. I also struggle to imagine how we’d reasonably decide to remove it from main. I’d be glad to elaborate on any of this if it matters. Ultimately, too much of the extended external demands on these (mostly) volunteers, including asking for more PEPs, feel like busy work for a project with a demonstrated discipline, a very focused impact on the CPython codebase, and where the only user-facing impact is faster execution. It seems like we’re swinging too far to the side of process and deliberation, at least in this case. We run the risk of driving away contributors and turning Python into a project in which mostly only enterprise teams participate. I don’t think we need to follow the lead of all the other major languages in this. (Disclosure: I worked full-time for over 4 years on the “faster CPython” team at Microsoft. (The company didn’t dictate any of our CPython work.) I wasn’t involved in the JIT work there, other than some code review and other supporting work, like benchmarking.) --- _[View the full topic](https://discuss.python.org/t/pep-836-jit-go-brrr-the-path-to-a-supported-jit-compiler-for-cpython/108010)._