[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-pythons-jit-future-hangs-on-new-pep-en":3,"article-related-pythons-jit-future-hangs-on-new-pep-en":33,"series-industry-59cc7315-b242-44f4-96ea-4adce886cf9e":86},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":25,"views":29,"created_at":30,"published_at":31,"topic_cluster_id":32},"59cc7315-b242-44f4-96ea-4adce886cf9e","pythons-jit-future-hangs-on-new-pep-en","Python’s JIT future hangs on a new PEP","\u003Cp data-speakable=\"summary\">Python’s JIT compiler is on hold until the project gets a new PEP.\u003C\u002Fp>\u003Cp>The Python steering council has put the JIT compiler project in limbo, and the outcome matters because Python 3.15 had already promised an 8-9 percent geometric mean speedup on x86-64 Linux. Here are the four most important takeaways for developers following the debate.\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Item\u003C\u002Fth>\u003Cth>Status\u003C\u002Fth>\u003Cth>Key number\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Python 3.15 JIT\u003C\u002Ftd>\u003Ctd>Experimental, paused\u003C\u002Ftd>\u003Ctd>8-9% speedup\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Deadline to act\u003C\u002Ftd>\u003Ctd>PEP required\u003C\u002Ftd>\u003Ctd>6 months\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Default setting\u003C\u002Ftd>\u003Ctd>Disabled\u003C\u002Ftd>\u003Ctd>PYTHON_JIT=1\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Release timing\u003C\u002Ftd>\u003Ctd>Feature-frozen\u003C\u002Ftd>\u003Ctd>October\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>1. The JIT is no longer moving forward in main\u003C\u002Fh2>\u003Cp>The steering council has asked for a suspension of new JIT development in Python’s main branch until a new PEP is created and accepted. Bug fixes and security fixes can still land, but feature work is effectively frozen for now.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781389066269-7pur.png\" alt=\"Python’s JIT future hangs on a new PEP\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>That is a major shift for a project that had been treated as one of the headline additions to Python 3.15. If no approved proposal arrives within six months, the current JIT code is expected to be removed from main.\u003C\u002Fp>\u003Cul>\u003Cli>New feature work: paused\u003C\u002Fli>\u003Cli>Bug and security fixes: allowed\u003C\u002Fli>\u003Cli>Removal trigger: no approved PEP in 6 months\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>2. Python 3.15’s speed claim is still real, but experimental\u003C\u002Fh2>\u003Cp>The JIT was expected to help Python 3.15 deliver an 8-9 percent geometric mean performance improvement over standard CPython on x86-64 Linux. That number is one reason the announcement caught people off guard.\u003C\u002Fp>\u003Cp>But the compiler is still experimental and disabled by default. To use it, developers have to set \u003Ccode>PYTHON_JIT=1\u003C\u002Fcode> in the environment, which keeps the feature opt-in rather than part of the normal runtime path.\u003C\u002Fp>\u003Cul>\u003Cli>Target platform: x86-64 Linux\u003C\u002Fli>\u003Cli>Reported gain: 8-9% geometric mean\u003C\u002Fli>\u003Cli>Default state: off\u003C\u002Fli>\u003Cli>Enablement: environment variable\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>3. The process complaint is about more than paperwork\u003C\u002Fh2>\u003Cp>The council says the JIT should not have been merged without a proper PEP for a change of this scope. The existing PEP 744 is informational, and the council says it leaves open questions that need clearer answers before the project can keep advancing.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781389065134-7ynm.png\" alt=\"Python’s JIT future hangs on a new PEP\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>Those questions include who maintains the JIT, how it fits with CPython tooling, what success looks like, and how it relates to third-party JIT efforts. In other words, the issue is not just approval mechanics, but whether the project has a stable long-term shape.\u003C\u002Fp>\u003Cul>\u003Cli>Maintenance ownership\u003C\u002Fli>\u003Cli>Tooling compatibility\u003C\u002Fli>\u003Cli>Success metrics\u003C\u002Fli>\u003Cli>Relationship to other JITs\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>4. The JIT team wants time, not a reset\u003C\u002Fh2>\u003Cp>Key contributor Mark Shannon said stopping all development until a PEP is accepted puts the team in an awkward position, because it creates pressure to write a new proposal quickly without enough time for community discussion. He said a new PEP was already planned for later this year, when the performance case would be stronger.\u003C\u002Fp>\u003Cp>Shannon also warned that a moratorium could slow momentum and cost the project new contributors. He said working in a fork would be difficult because the optimization machinery creates large code differences that are hard to manage.\u003C\u002Fp>\u003Cul>\u003Cli>Requested grace period: one to two months\u003C\u002Fli>\u003Cli>Risk named by Shannon: loss of momentum\u003C\u002Fli>\u003Cli>Forking concern: large code divergence\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>5. The likely compromise is a more general JIT infrastructure\u003C\u002Fh2>\u003Cp>Steering council member Pablo Galindo Salgado said the goal is not to force competing proposals, but he did point toward a JIT infrastructure that can support multiple implementation strategies. That hints at a preference for a less tightly coupled design.\u003C\u002Fp>\u003Cp>Another council member, Donghee Na, said the current experimental JIT needs an official PEP and that this is a good time to review different approaches. Thomas Wouters added that the six-month deadline has some flexibility, though he stressed that the work needs to be taken seriously.\u003C\u002Fp>\u003Cul>\u003Cli>Possible direction: shared JIT infrastructure\u003C\u002Fli>\u003Cli>Design preference: less coupling to one strategy\u003C\u002Fli>\u003Cli>Deadline: flexible, not imaginary\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How to decide\u003C\u002Fh2>\u003Cp>If you care about near-term Python speedups, watch the PEP process and the six-month clock. If you care more about long-term maintainability, the council’s concerns about ownership, tooling, and success criteria are the real story.\u003C\u002Fp>\u003Cp>For users, the practical answer is simple: the JIT is still experimental, still off by default, and still not something most deployments need to touch today. For CPython contributors, the next PEP will decide whether this becomes a supported path or a cautionary tale.\u003C\u002Fp>","4 things Python developers need to know about the JIT pause, the six-month clock, and what it means for Python 3.15.","www.theregister.com","https:\u002F\u002Fwww.theregister.com\u002Fdevops\u002F2026\u002F06\u002F08\u002Fpython-jit-compiler-may-be-removed\u002F5252079",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781389066269-7pur.png","industry","en","3dd972ed-9161-445b-aa09-0e3b2b62cd76",[17,18,19,20,21,22,23,24],"Python","CPython","JIT compiler","PEP 744","Python 3.15","open source","performance","steering council",[26,27,28],"The Python steering council has paused new JIT development in main until a new PEP is approved.","Python 3.15’s JIT was expected to deliver an 8-9% geometric mean speedup, but it remains experimental and off by default.","The dispute is about process, maintenance, tooling compatibility, and whether the JIT should be a shared infrastructure layer.",0,"2026-06-13T22:17:20.722886+00:00","2026-06-13T22:17:20.715+00:00","c69ef824-9d39-4d1f-b791-7b473db93fbb",{"tags":34,"relatedLang":45,"relatedPosts":49},[35,37,39,41,43],{"name":19,"slug":36},"jit-compiler",{"name":17,"slug":38},"python",{"name":21,"slug":40},"python-315",{"name":20,"slug":42},"pep-744",{"name":18,"slug":44},"cpython",{"id":15,"slug":46,"title":47,"language":48},"python-jit-pause-pep-3-15-zh","Python JIT 暫停後，3.15 先看這 5 件事","zh",[50,56,62,68,74,80],{"id":51,"slug":52,"title":53,"cover_image":54,"image_url":54,"created_at":55,"category":13},"d5852d0a-88c2-4d93-869f-03e83e76424c","jensen-huang-lg-ai-cooperation-five-bets-en","Jensen Huang’s LG deal spans five AI bets","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781399872771-tzny.png","2026-06-14T01:17:22.547908+00:00",{"id":57,"slug":58,"title":59,"cover_image":60,"image_url":60,"created_at":61,"category":13},"59e63043-a1a2-4dab-a053-d64991e3f1cf","nvidia-sk-group-expand-ai-ties-co-development-en","Nvidia and SK Group expand AI ties into co-development","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781398976022-afrl.png","2026-06-14T01:02:30.330777+00:00",{"id":63,"slug":64,"title":65,"cover_image":66,"image_url":66,"created_at":67,"category":13},"f50df767-8d6e-4ceb-886f-f8cb610a9f19","llm-wiki-compiler-raw-sources-to-wiki-en","llm-wiki-compiler turns raw sources into a wiki","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781389970201-6yvr.png","2026-06-13T22:32:23.002929+00:00",{"id":69,"slug":70,"title":71,"cover_image":72,"image_url":72,"created_at":73,"category":13},"0dc4656a-15f8-48ec-bcdf-f9aca8ac32db","ukraines-ai-war-network-faster-combat-en","Ukraine’s AI war network points to faster combat","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781363881146-5og8.png","2026-06-13T15:17:22.601823+00:00",{"id":75,"slug":76,"title":77,"cover_image":78,"image_url":78,"created_at":79,"category":13},"49f998be-b115-4206-977f-40ca930d85ce","anthropic-governance-market-story-en","Anthropic’s governance debate is now a market story","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781362977290-fdxs.png","2026-06-13T15:02:18.113309+00:00",{"id":81,"slug":82,"title":83,"cover_image":84,"image_url":84,"created_at":85,"category":13},"109408c4-f132-4827-a4a9-0332b51a0bb7","mastercard-ai-payments-solana-bull-case-en","Mastercard’s AI Payments Move Is A Solana Bull Case, Not A Hype Story","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781360267532-n3ga.png","2026-06-13T14:17:21.37458+00:00",[87,92,97,102,107,112,117,122,127,132],{"id":88,"slug":89,"title":90,"created_at":91},"d35a1bd9-e709-412e-a2df-392df1dc572a","ai-impact-2026-developments-market-en","AI's Impact in 2026: Key Developments and Market Shifts","2026-03-25T16:20:33.205823+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"5ed27921-5fd6-492e-8c59-78393bf37710","trumps-ai-legislative-framework-en","Trump's AI Legislative Framework: What's Inside?","2026-03-25T16:22:20.005325+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"e454a642-f03c-4794-b185-5f651aebbaca","nvidia-gtc-2026-key-highlights-innovations-en","NVIDIA GTC 2026: Key Highlights and Innovations","2026-03-25T16:22:47.882615+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"0ebb5b16-774a-4922-945d-5f2ce1df5a6d","claude-usage-diversifies-learning-curves-en","Claude Usage Diversifies, Learning Curves Emerge","2026-03-25T16:25:50.770376+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"69934e86-2fc5-4280-8223-7b917a48ace8","openclaw-ai-commoditization-concerns-en","OpenClaw's Rise Raises Concerns of AI Model Commoditization","2026-03-25T16:26:30.582047+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"b4b2575b-2ac8-46b2-b90e-ab1d7c060797","google-gemini-ai-rollout-2026-en","Google's Gemini AI Rollout Extended to 2026","2026-03-25T16:28:14.808842+00:00",{"id":118,"slug":119,"title":120,"created_at":121},"6e18bc65-42ae-4ad0-b564-67d7f66b979e","meta-llama4-fabricated-results-scandal-en","Meta's Llama 4 Scandal: Fabricated AI Test Results Unveiled","2026-03-25T16:29:15.482836+00:00",{"id":123,"slug":124,"title":125,"created_at":126},"bf888e9d-08be-4f47-996c-7b24b5ab3500","accenture-mistral-ai-deployment-en","Accenture and Mistral AI Team Up for AI Deployment","2026-03-25T16:31:01.894655+00:00",{"id":128,"slug":129,"title":130,"created_at":131},"5382b536-fad2-49c6-ac85-9eb2bae49f35","mistral-ai-high-stakes-2026-en","Mistral AI: Facing High Stakes in 2026","2026-03-25T16:31:39.941974+00:00",{"id":133,"slug":134,"title":135,"created_at":136},"9da3d2d6-b669-4971-ba1d-17fdb3548ed5","cursors-meteoric-rise-pressures-en","Cursor's Meteoric Rise Faces Industry Pressures","2026-03-25T16:32:21.899217+00:00"]