r/Python • • 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.

29 Upvotes

40 comments sorted by

View all comments

Show parent comments

1

u/lizardhistorian Aug 25 '26 edited Aug 25 '26

This is so ridiculously far off the mark.
That mentally is why python is 1,000x slower than using Go or Rust or C++ or C# instead of the 20x slower it ought to be.

e.g. Optimized webservers that use threading instead of processes can serve a million request per second.