pex: switch to SCIE binary instead of PEX #21755
Draft
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.
Switch to the SCIE distribution of Pex (embedded Python interpreter) instead of using the PEX distribution of PEX.
One motive is to avoid a Pip bootstrapping problem which can result in the vendored Pip being used which does not support
--keyring-provider
which will be needed for AWS CodeArtifact support being developed here. The 3.12.x+ Python interpreter in the Pex SCIE is new enough to have a Pip which supports that option.There are general benefits as well for reducing the variance across systems in terms of only a single Python interpreter version being used to invoke Pex.