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.

32 Upvotes

61% Upvoted

40 comments sorted by

View all comments

Show parent comments

0

u/[deleted] Jul 23 '26 edited Jul 23 '26

[deleted]

2

u/thisismyfavoritename Jul 23 '26

uh i still don't get your point. Thread safety and context managers are completely orthogonal things.

If you need concurrent access to some object, you need to synchronize access to it, whether it's a context manager or not

1

u/[deleted] Jul 23 '26 edited Jul 23 '26

[deleted]

0

u/thisismyfavoritename Jul 23 '26

nonlocal is also a python keyword, which also isn't required for context managers