Bundled pip and setuptools wheels have to be verified manually at the moment when they are upgraded.
We can automate this by comparing their checksums to ones provided by Warehouse’s JSON API (e.g., https://pypi.org/pypi/pip/json.)
Since such a check requires network activity and not to slow down tests, creating a GitHub Actions workflow that runs only when the files are changed is a good option.
Activity
illia-v commented on Mar 14, 2022
Bundled pip and setuptools wheels have to be verified manually at the moment when they are upgraded.
We can automate this by comparing their checksums to ones provided by Warehouse’s JSON API (e.g., https://pypi.org/pypi/pip/json.)
Since such a check requires network activity and not to slow down tests, creating a GitHub Actions workflow that runs only when the files are changed is a good option.
I suggested this in #30178 (comment) originally.
gh-91172: Create a workflow for verifying bundled pip and setuptools (G…
pythongh-91172: Create a workflow for verifying bundled pip and setup…
pythongh-91172: Create a workflow for verifying bundled pip and setup…
pythongh-91172: Create a workflow for verifying bundled pip and setup…
gh-91172: Create a workflow for verifying bundled pip and setuptools (G…
gh-91172: Create a workflow for verifying bundled pip and setuptools (G…
gh-91172: Create a workflow for verifying bundled pip and setuptools (G…
gh-91172: Create a workflow for verifying bundled pip and setuptools (G…
pythongh-91172: Create a workflow for verifying bundled pip and setup…
gh-91172: Create a workflow for verifying bundled pip and setuptools (G…
ambv commented on Jun 22, 2022
This is now live on all branches from 3.7 to 3.12. Thanks! ✨ 🍰 ✨
Revert 30935 defer bpo45162 to 312 (#94285)