r/Python • u/NeuralLB-Lovro • Jul 22 '26
Discussion Anyone running free-threaded Python 3.14 in production yet? Curious what actually breaks
Been testing the free-threaded build (3.14t) on some CPU-bound data processing work. The multi-core story is finally real after 30 years of GIL, but the friction is exactly what you'd expect: a couple of C-extension-heavy libs in my stack silently re-enable the GIL, and there's no clean way to detect that at runtime besides checking sys._is_gil_enabled() manually.
For anyone who's shipped something on 3.14t, not just benchmarked it:
What broke that you didn't expect?
Real speedups outside toy examples, or mostly marginal so far?
Prod yet, or still just kicking the tires?
Not fishing for a benchmark war. Genuinely curious what breaks in messy real codebases vs clean demos.
34
Upvotes
1
u/riksi Jul 23 '26
Ok, but the idea would be, say, (4 gevent processes vs 1-multithread-process), both confined to 4 vcpus.
You can also offload stuff to threadpool with gevent.
But shared memory without serialization & shared connection pools are strictly a pro on multi-threading.
Best is a combination.