Skip to content

Drop MD5 checksums in favour of SHA-256#347

Draft
hugovk wants to merge 1 commit intopython:mainfrom
hugovk:rm-md5
Draft

Drop MD5 checksums in favour of SHA-256#347
hugovk wants to merge 1 commit intopython:mainfrom
hugovk:rm-md5

Conversation

@hugovk
Copy link
Member

@hugovk hugovk commented Feb 27, 2026

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.

Copy link
Collaborator

@sethmlarson sethmlarson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I assume we don't want to disturb old pages by "back-filling" SHA-256 values to those releases.

@hugovk
Copy link
Member Author

hugovk commented Feb 27, 2026

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants