fix #1652: Use GitHub API for standalone python checksums #1662
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.
changelog.d/(if the patch affects the end users)Summary of changes
Since the 20250708 release, the python-build-standalone project does not provide checksum files for individual artifacts, but rather a single
SHA256SUMSmanifest file containing checksums for all artifacts. However, since June 3, the GitHub APIdirectly provides checksums for release artifacts.
Because we always fetch the latest release and it's been over a month since the last cached index file, we can just save the checksums in out cached index of Python versions.
fixes #1652
closes #1655
Test plan
Tested by running
pipx install --python python3.10 --fetch-missing-pythonon a machine without python3.10