-
-
Notifications
You must be signed in to change notification settings - Fork 291
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 should not re-exec when the current interpreter satifies constraints #709
Labels
Comments
Noticed working pantsbuild/pants#7591 |
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Jun 24, 2019
Ensure `PEX_PYTHON` and `PEX_PYTHON_PATH` are actually scrubbed from the environment of the pex process when re-exec'd fixing pex-tool#710. Also uniformize re-exec interpreter selection to ensure that the current interpreter is preferred when it meets any constraints fixing pex-tool#709. Fixes pex-tool#709 Fixes pex-tool#710
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Jun 25, 2019
Ensure `PEX_PYTHON` and `PEX_PYTHON_PATH` are actually scrubbed from the environment of the pex process when re-exec'd fixing pex-tool#710. Also uniformize re-exec interpreter selection to ensure that the current interpreter is preferred when it meets any constraints fixing pex-tool#709. Fixes pex-tool#709 Fixes pex-tool#710
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently Pex can re-exec against a new interpreter even when the current interpreter is on the PEX_PYTHON_PATH or PATH and matches any compatibility constraints. This should be avoided both for efficiency and to allow explicit control of the interpreter used to execute the pex.
The text was updated successfully, but these errors were encountered: