You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Include the SHA 256 hash of the pip wheel artifact used in ensurepip module and fail execution if the checksum doesn't match. This will serve as a protection mechanism allowing non-trusted contributors to contribute updates to artifacts and allow reviewers to quickly check in the PyPI UI whether the artifact has the correct checksum.
This feature request was spawned from this PR: #112517 which required a bit more reviewing work to be confident in the contributed artifact.
Has this already been discussed elsewhere?
I have already discussed this feature proposal on Discourse
Note that this would not imply that we should accept ensurepip upgrades from anyone other than the pip maintainers, so that we (pip) can delay pushing a pip release to ensurepip if we ever need to.
This will serve as a protection mechanism allowing non-trusted contributors to contribute updates to artifacts and allow reviewers to quickly check in the PyPI UI whether the artifact has the correct checksum.
We already have a protection mechanism in place in the form of a CI check.
Activity
pfmoore commentedon Dec 4, 2023
Note that this would not imply that we should accept ensurepip upgrades from anyone other than the pip maintainers, so that we (pip) can delay pushing a pip release to ensurepip if we ever need to.
pradyunsg commentedon Dec 4, 2023
We already have a protection mechanism in place in the form of a CI check.
https://github.com/python/cpython/blob/main/.github/workflows/verify-ensurepip-wheels.yml
sethmlarson commentedon Dec 4, 2023
Oh cool, this issue is probably not needed then. Thanks @pradyunsg!