r/Python • u/techiebaddie • 15h ago

Discussion I know I’m late, but Python 3.14.7 is out. Anyone actually upgraded yet?

I know I’m a little late to this, but I’ve been looking into Python 3.14.7 and something keeps bothering me.

The release itself looks solid. Python 3.14.7 was released on August 5 and is mainly a maintenance release with a lot of bug fixes and improvements.

But for people working on existing projects, the bigger question seems to be:

What makes you decide that it’s finally time to upgrade Python?

A new Python version sounds great until you have to check:

  • dependencies
  • C extensions
  • Docker images
  • CI/CD
  • production servers
  • test suites
  • old packages that nobody wants to touch

And Python 3.14 has some pretty interesting changes compared with 3.13, including officially supported free-threaded Python, t-strings, multiple interpreters, and the new compression.zstd module.

So I’m curious about real-world experience rather than release notes.

Have you upgraded to 3.14 yet?

If yes, what went smoothly and what broke?

If no, what’s the main reason you’re waiting?

0 Upvotes

10% Upvoted

6 comments sorted by

6

u/zzzthelastuser 15h ago

dude just upgrade and see if it works. There is no point in comparing random projects with vastly different environments and dependencies. Either it works for you or it doesn't.

1

u/techiebaddie 14h ago

Yep, fair point

1

u/Front_Swordfish5661 15h ago

Still on 3.13 here and probably staying for a while. My work project has this one internal library that nobody updated since like 2022 and I'm not touching that thing until absolutely forced. Docker image rebuilding alone takes half a day with our CI pipeline.

1

u/jsabater76 13h ago

I started my last API project using Django Ninja and I was already using 3.14. So. For me, it was just a patch update. No problems at all.

0

u/TraditionalTurnip630 15h ago

Tried 3.14.7 in testing last week. Data analytics stack (pandas, polars, numpy, sklearn) mostly worked fine. Free-threaded looked promising for multi-core jobs, zstd is nice for big files.

Few small issues: had to rebuild a couple old C-extension packages, Docker base images needed updating, one CI type-check failed. Nothing major.

Still waiting on full production upgrade. Team’s other services aren’t ready yet and 3.12/3.13 is stable, so no rush. If your pipeline is pure Python it’s worth testing.

0

u/DangerousTrickq 7h ago

Finally upgraded staging, free-threaded build broke my C extensions but zstd module totally worth it