"Python 3.14 is here. If you haven't done so, it's time to update your projects to test against 3.14. The following procedure is what I'm following for a handful of projects. Your process of course may be different if you use different tools. Honestly, I'm partly writing this down so I don't have to remember it all in a year when 3.15 rolls around."
"Installing with uv While it's true that creating a virtual environment with uv venv .venv --python 3.14 will install 3.14 if it isn't already there, you still gotta run uv self update. So I just usually install it while I'm at it. Installing with the python.org installer If you're not on the uv bandwagon yet, it's still hard to beat downloading and installing from python.org. Make sure you're code is the latest and greatest"
"git status - check to see if anything is currently modified from the repo. If it is, you can do a quick git stash -u to save that work for later. Or toss it with git reset --hard HEAD Or check it in if you're on a branch and want to save your work. git checkout main Set up a branch to do the mods Add "py314" to tox.ini Example:"
Update projects to test against Python 3.14 by installing a local Python 3.14 and adjusting configuration and CI. Use uv to create a venv with uv venv .venv --python 3.14 and run uv self update, or download and install from python.org. Ensure working tree is clean with git status, use git stash -u or git reset --hard HEAD as needed, and checkout main. Create a branch for modifications. Add py314 to tox.ini envlist and add 'Programming Language :: Python :: 3.14' to pyproject.toml classifiers. Use troml carefully (reorder versions and avoid adding 3.15 prematurely). Add 3.14 to CI test matrices.
Read at Pythontest
Unable to calculate read time
Collection
[
|
...
]