# PEP 744: JIT Compilation **URL:** \ **Category:** PEPs\ **Created:** [April 12, 2024, 12:33am UTC](https://discuss.python.org/t/pep-744-jit-compilation/50756 "2024-04-12T00:33:50Z")\ **Posts on this page:** 1\ **Showing post:** 33
**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\ **Post date:** [April 17, 2024, 4:38pm UTC](https://discuss.python.org/t/pep-744-jit-compilation/50756/33 "2024-04-17T16:38:41Z")
> [@brandtbucher](#): > > Yep, something like that definitely makes sense. It’s currently actually possible (for testing), but having both a more ergonomic way of doing this at runtime (in the `sys` module) as well as environment variable or command-line options to control is something I’ve been thinking about. Would it be possible to have a a way to configure Python to **disable the JIT by default** , but have a command line options (ex: env var and/or CLI option) to enable it? The use case is to ship a single binary in Fedora with JIT disabled, to avoid any issues with the JIT by default, but let _early adopters_ to play with it. Example: - `python3.13` runs Python without the JIT (disabled) - `python3.13 -X jit` runs Python with the JIT enabled Fedora discussion: [https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/O3QSAOTIZKNSETB4B6NZK4CG5LGE5FRA/](https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/O3QSAOTIZKNSETB4B6NZK4CG5LGE5FRA/) --- _[View the full topic](https://discuss.python.org/t/pep-744-jit-compilation/50756)._