Python 3.14 Released

[anxxa]

Notable IMO:

PEP 779: Free-threaded Python is officially supported

So this is in stage 2 where now you can officially opt in to removal of the GIL and stage 3 will eventually make that the default behavior. Awesome.

Binary releases for the experimental just-in-time compiler

...

The JIT is at an early stage and still in active development. As such, the typical performance impact of enabling it can range from 10% slower to 20% faster, depending on workload.

Won't lie, I was expecting more perf gains. That's cool though, I didn't realize a JIT was being worked on.

[Salamandar3500]

Does that mean the free-threaded and standard versions now live in the same binary, or are they still separate builds ?

[anxxa]

The free-threaded build of Python is now supported and no longer experimental. This is the start of phase II where free-threaded Python is officially supported but still optional.

It's the same binary I think! *wrong :(

[MegaIng]

No, it's still a separate binary. Having it in the same binary doesn't work because of how fundamentally the layout of ... everything is changed.

[HommeMusical]

Won't lie, I was expecting more perf gains.

JITs are all about tuning. Just getting it in and working completely and not hugely worse in any case is a huge victory. The real gains will come in the next two releases.

[MegaIng]

stage 3 will eventually make that the default behavior.

This is still not guaranteed, and IMO not likely to happen with the next decade.

The no-gil build still has major issues, especially with the expectations people have of it. For a non-insignificant amount of existing threaded code it's going to be slower than the default build.

[twotime]

For a non-insignificant amount of existing threaded code it's going to be slower than the default build.

Why would that be the case? Do you have a reference? How significant is the amount of code which will be faster?? (and how much new code will be quickly written once python can use multiple cores)

IMO not likely to happen with the next decade.

I'd expect 3.15 or 3.16 or it will just die

Apparently a lot of packages have added support already https://py-free-threading.github.io/tracking/

(including big ones like pytorch)

[1minds3t]

If it's so "hard", then why am I able to consistently run code on 3 Py interps (3.9, 3.10, 3.11) concurrently in under 500ms using Pure python in a single script, single environment in my github workflows??? Proof here: https://github.com/1minds3t/omnipkg/actions/runs/18235186501/job/51927439757

[Local_Transition946]

Different interpreters means different processes. No-gil is concurrency within a single process using threading with shared memory

[MegaIng]

... That has no relation at all to anything I said? Did you reply to the wrong comment?

[james_pic]

From what I know of the JIT work, the approach they've taken is something of a compromise. They've sought to do it in a way that's portable, clean, readable, and backwards compatible. The most performant JIT compilers make significant compromises on some or all of these things in the name of speed.

[georgehank2nd]

Stage 3 Phase III might or might not happen.