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

Export venvs for a matrix of multiple python interpreters #20516

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cognifloyd
Copy link
Member

@cognifloyd cognifloyd commented Feb 9, 2024

Extracted #21087 as pre-work for this PR.

Closes #15817

@cognifloyd cognifloyd force-pushed the cognifloyd/export-matrix branch from 391543a to e7db0e6 Compare June 19, 2024 04:14
@cognifloyd cognifloyd added category:new feature backend: Python Python backend-related issues labels Jun 19, 2024
@cognifloyd cognifloyd force-pushed the cognifloyd/export-matrix branch from e7db0e6 to 3eb5463 Compare June 19, 2024 05:07
cognifloyd added a commit that referenced this pull request Jun 20, 2024
Instead of relying on the implicit pex interpreter resolution--based on
interpreter_constraints--this PR makes the export pre-calculate which
interpreter to use.

This has the benefit of allowing pants to provide the python interpreter
(eg with pyenv) if configured to do so. Without this, the exports can
only use pre-installed interpreters.

To make this work, I had to prevent the injection of
`PexRequest.interpreter_constraints` when `PexRequest.python` is set.

This refactor is pre-work for #20516.
@cognifloyd cognifloyd force-pushed the cognifloyd/export-matrix branch from 3eb5463 to 7ab6def Compare June 23, 2024 03:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend: Python Python backend-related issues category:new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Export a matrix of resolve+python versions
1 participant