Some of the libraries I need don't have packages for the newest Python version yet. Is there a useful rule of thumb for how long to wait, or does it just depend on the project?
How long do you wait before using a new Python version?
Answers
I'd make the dependency list the deciding factor, not the calendar. Check whether the packages you actually use support the new version, then run your project's tests against it. One missing library can make the wait much longer than three or six months.
You don't have to move every project at once, either. Use a supported Python version that works for each one.
Reply to this answer
For production, staying one minor version behind is a pretty simple rule. It gives the ecosystem some time to catch up without committing you to waiting for a specific number of months. Still check the support status of the version you're running so it doesn't reach end of life unnoticed.
Reply to this answer
Testing and adopting don't have to happen at the same time. Add the new version to your automated test runs when practical, while keeping production on your current version. That gives you an early look at dependency or compatibility problems without forcing a migration.
For a library, you can also test across the Python versions you support. A prerelease can be useful for spotting problems early, though missing packages may make those tests incomplete.
Reply to this answer
A slower option is to plan upgrades around Python's support lifecycle. Some teams wait until their current version moves into security-only support before upgrading. That can be reasonable if stability matters more than new features, but don't leave the move until the current version is nearly end of life.
Reply to this answer
Your deployment environment matters too. If your servers run a long-term support Linux release, its upgrade cycle may be a convenient time to reconsider Python as well. There's less reason to rush if the new features don't help your project, especially when those features need library support to be useful.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_w47!clayratchet.8:
And if a dependency still hasn't caught up by then, being one version behind isn't a guarantee. You'll need to check that project separately.