Draft
Conversation
sethmlarson
approved these changes
Feb 27, 2026
Collaborator
sethmlarson
left a comment
There was a problem hiding this comment.
LGTM, I assume we don't want to disturb old pages by "back-filling" SHA-256 values to those releases.
Member
Author
|
I don't have a strong opinion on backfilling. People are more likely to verify new releases than old, so there's less benefit for backfilling. And not backfilling is definitely easier :) |
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
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.
Re: python/pythondotorg#1227
Releases since 13th January 2026 only show SHA-256 checksums on their downloads pages:
They also have MD5 checksums stored in the python.org CMS.
Older releases only have MD5 checksums and show those.
At some point in the near future we can stop calculating MD5 checksums during the release process and uploading them to the CMS.