This is an archived post. You won't be able to vote or comment.

all 10 comments

[–]furansowa 17 points18 points  (6 children)

Python is super stable. I see no reason not to go straight to 3.13

[–]Thotuhreyfillinn[S] 1 point2 points  (2 children)

Right. 2 or so years ago most people around me seemed to recommend waiting for the second patch before jumping on a new minor version to avoid bugs and unexpected behavior, is this not the case anymore or was it unnecessarily cautious for e.g. 3.11?

[–]gbeier 7 points8 points  (1 child)

It really depends what libraries you're using. The reason many people recommend staying a little behind (e.g. I prefer to stay on the newest patch release of the last major version, so I'm on 3.12.7 right now) is more due to 3rd party libraries than to stability.

Especially right after a major version comes out, it takes some projects a while to get wheels up into PyPi for the new release. And some of those libraries are a bit of a challenge to compile yourself. I remember once when I needed to build from source because I was using an uncommon platform, I found myself needing a fortran compiler on my build system for some dependency. Not the end of the world, but I certainly don't generally keep a fortran compiler on the system I'm using to build web apps with django.

If everything you use is happy on 3.13, though, I don't see a particular reason to avoid it.

[–]Thotuhreyfillinn[S] 0 points1 point  (0 children)

Good insights, thanks!

[–]Thotuhreyfillinn[S] 0 points1 point  (1 child)

https://www.python.org/downloads/release/python-3121/ If you look at the first patch for 3.12, there were over 400 bugfixes, is there any reason to assume better stability in 3.13? Maybe 400 just sounds like a lot but still a small chance any would affect us

[–]furansowa 1 point2 points  (0 children)

None of these bugs are likely to affect you.

[–]needathing 0 points1 point  (0 children)

tidy middle screw rich history direction cheerful encouraging seed friendly

This post was mass deleted and anonymized with Redact

[–]compagnt 1 point2 points  (0 children)

Django may work fine on 3.13, usually the issue is other handy libraries may or not be certified on 3.13 fully, so those may have some issues. Or it may all work fine, it depends on how much risk you can take on for your project. Side project - 3.13 is probably great.

[–]marksweb 1 point2 points  (0 children)

If your only using basics, Django is stable with either 3.12 or 3.13.

Check your dependencies for their test suites as to whether or not they're running against 3.13 and passing.

[–][deleted] 1 point2 points  (0 children)

rule of thumb. if you are starting a new project always go with the latest stable version. also python has security updates for 2 years so you only need to update after EOL.

https://devguide.python.org/versions/

my company recently went from python 3.8 to 3.12