-
-
Notifications
You must be signed in to change notification settings - Fork 292
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
The --venv mode hash scheme can be insensitive to interpreter. #1422
Labels
Comments
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Aug 28, 2021
This supports some up-coming test changes in the fix for pex-tool#1422.
jsirois
added a commit
that referenced
this issue
Aug 28, 2021
This supports some up-coming test changes in the fix for #1422.
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Aug 29, 2021
Previously, requesting a PEX_PYTHON with an absolute path to an interpreter might not fail if the interpreter was invalid or if it was valid but not on a requested PEX_PYTHON_PATH. Fix up both behaviors and close pex-tool#431 as no longer relevant or well guided. Clarifies behaviors pex-tool#1422 should support in interpreter selection effects on `--venv` mode venv directory hashes.
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Aug 29, 2021
Previously the venv dir hash locked unconstrained PEXes into a venv using the interpreter they were first run with. Now, when a `--venv` mode PEX is either unconstrained or only constrained by a PEX_PYTHON_PATH that admits the interpreter being used to execute the `--venv` mode PEX, that interpreter is recorded in the venv dir hash to differentiate a venv dedicated to that interpreter. Fixes pex-tool#1422
jsirois
added a commit
that referenced
this issue
Aug 30, 2021
Previously, requesting a PEX_PYTHON with an absolute path to an interpreter might not fail if the interpreter was invalid or if it was valid but not on a requested PEX_PYTHON_PATH. Fix up both behaviors and close #431 as no longer relevant or well guided. Clarifies behaviors #1422 should support in interpreter selection effects on `--venv` mode venv directory hashes.
jsirois
added a commit
that referenced
this issue
Aug 31, 2021
Previously the venv dir hash locked unconstrained PEXes into a venv using the interpreter they were first run with. Now, when a `--venv` mode PEX is either unconstrained or only constrained by a PEX_PYTHON_PATH that admits the interpreter being used to execute the `--venv` mode PEX, that interpreter is recorded in the venv dir hash to differentiate a venv dedicated to that interpreter. Fixes #1422
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summarized here:
The text was updated successfully, but these errors were encountered: