Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pex: switch to SCIE binary instead of PEX #21755

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

tdyas
Copy link
Contributor

@tdyas tdyas commented Dec 12, 2024

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.

@tdyas tdyas added category:internal CI, fixes for not-yet-released features, etc. release-notes:not-required PR doesn't require mention in release notes labels Dec 12, 2024
@tdyas
Copy link
Contributor Author

tdyas commented Dec 12, 2024

fyi @cburroughs

@tdyas
Copy link
Contributor Author

tdyas commented Dec 12, 2024

The draft needs a bunch of work to stop trying to find compatible Python interpreters for Pex invocations since it now comes with its own interpreter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:internal CI, fixes for not-yet-released features, etc. release-notes:not-required PR doesn't require mention in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant