Use Python 3.13 as the default Python version for new apps #1715
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously if a new app did not specify a Python version (e.g. via a
.python-version
file), then the buildpack would default to the latest Python 3.12 release.Now the buildpack will use the latest Python 3.13 release.
This does not affect:
Use-cases involving new apps that aren't compatible with Python 3.13 will now need to specify Python 3.12 explicitly:
https://devcenter.heroku.com/articles/python-support#specify-a-python-version
However most apps should be compatible, since Python 3.13 was released a couple of months ago (2024-10-07), does not contain significant breaking changes over Python 3.12, and has been happily used by the python-getting-started project since 2024-10-10.
See:
https://docs.python.org/3.13/whatsnew/3.13.html
Note: When using Python 3.13, the buildpack does not install setuptools, wheel or the sqlite headers/CLI, hence those diffs to the test fixtures.
GUS-W-14846972.