Add the python interpreter as a hidden dep of a pex file #626
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a unique python setup. We distribute it hermetically via an internal tool (similar to dotslash), then we set up our
python
toolchain to return aPythonToolchainInfo
whoseinterpreter
andhost_interpreter
fields point to a shell script calledpython_shim.sh
that is created viactx.actions.write()
, in order to properly set up the venv and do some other things to make it hermetic.Later, if you call
python_binary
, it generates a pex file which contains a line like this at the beginning:Presently this is broken because the
cmd_args
to execute the pex file does not have an action dependency on the interpreter, and so it complains that it cannot findpython_shim.h
. This PR makes it work