Support extracting PexResolveInfo from a Pex. #11693
Merged
Conversation
This file contains 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
There was no reason this was limited to just VenvPex. This allows, for example, resolving a Pex, testing its contents, and then assembling a VenvPex that uses its resolve via the pex_path. [ci skip-rust] [ci skip-build-wheels]
Previously Pexes got created with --include-tools, now they do not. This emphasises that PexRepositoryInfo can be obtained for vanilla Pexes. [ci skip-rust] [ci skip-build-wheels]
stuhood
approved these changes
Mar 15, 2021
Merged
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.
There was no reason this was limited to just VenvPex. This allows, for
example, resolving a Pex, testing its contents, and then assembling a
VenvPex that uses its resolve via the pex_path.
[ci skip-rust]
[ci skip-build-wheels]