Generate table of active Python releases #2862
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Generate the table of active Python releases.
This means we can remove another manual step from the release process.
Get the releases data from the PEPs API: https://peps.python.org/api/#release-cycle-json
We were using another PEPs API file -- https://peps.python.org/api/#python-releases-json -- elsewhere. Let's refactor that to use the other one, because the file is a bit smaller.
Before
https://www.python.org/downloads/
After
And because this is getting up-to-date data from the API, it's more accurate. For example, I had initially copied and pasted the wrong 3.15 first release date (2026-10-07) when it's really 2026-10-01.