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.

Sign up for GitHub

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

Jump to bottom

Improve ergonomics of pex interpreter selection #10662

Closed
benjyw opened this issue Aug 20, 2020 · 1 comment
Closed

Improve ergonomics of pex interpreter selection #10662

benjyw opened this issue Aug 20, 2020 · 1 comment
Assignees
@benjyw
Milestone
2.0.0 blocker

Comments

@benjyw
Copy link
Contributor

benjyw commented Aug 20, 2020 •
edited
Loading

How a specific Python interpreter is chosen at build time and at runtime is hard for users to reason about, and can interact poorly with local system conditions.

Related:
#7508
#10489
#10648
@benjyw benjyw self-assigned this Aug 20, 2020
@benjyw benjyw added this to the 2.0.0rc0 milestone Aug 20, 2020
@tdyas
Copy link
Contributor

tdyas commented Sep 3, 2020

I hit a similar issue today when building a pex. The venv in which toolchain repo was running is 3.8.5 but pants/pex was choosing 3.8.2 for the pex and not finding it. Finally had to pyenv install 3.8.2 and make available with pyenv global to work around the problem.

@benjyw benjyw closed this as completed Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benjyw benjyw

Labels
None yet
Projects
None yet
Milestone
2.0.0 blocker
Development

No branches or pull requests
2 participants
@benjyw @tdyas