- Sponsor
-
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
Kill off PEX_PYTHON #431
Comments
See #53 - isn't there sometimes a use case for "please use exactly this python"? Or is there an alternative way to get that functionality? |
The idea here is that PEX_PYTHON_PATH is a graduated variant of PEX_PYTHON that says "Use user-supplied constraints and exec with the minimum compatible interpreter from this list of Python interpreters". As of right now, PEX_PYTHON_PATH with only one interpreter will effectively accomplish the same thing as PEX_PYTHON. |
Although what @CMLivingston says is True, this is ingrained enough in scripts and a useful enough distinction to meet reasonable user expectations in practice (PATH variables don't normally support the full path to a binary, just to the parent dir), that I think its worth keeping. |
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.
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.
The pex runtime currently supports a configuration for a PEX_PYTHON variable in a pexrc file. This variable allows a user to define a Python Interpreter to override the default interpreter when executing the pex.
This has been replaced by a PEX_PYTHON_PATH variable, that allows the user to specify a colon-separated list of paths to Python interpreters with the aim of being able support interpreter selection against a list of interpreter override candidates.
The goal of this issue is to completely kill off PEX_PYTHON support in the pex codebase in favor of the new PEX_PYTHON_PATH pexrc variable.
The text was updated successfully, but these errors were encountered: