Pass --only-binary :all: when upgrading pip - #406
Open
mara004 wants to merge 2 commits into
Open
Conversation
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
2 participants
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.
This would alleviate some of our concerns from actions/setup-python#1346 in a very straightforward way, by preventing possible setup-time code execution, so that a caller's supply chain would be unaffected by setup-python's auto-updated pip unless it is actually invoked.
AFAIK, it can be taken for granted that every valid pip release includes a wheel package. If a pip release included only an sdist, that might be either accidental or malicious, and deserve investigation before being automatically installed to millions of callers.
Disclaimer: I'm not aware of a good way to actually test the integration, esp. windows