[Bugfix] Pass PYTHONPATH from setup.py to CMake #7730
Merged
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.
In clean build environments such as
cibuildwheel
, build dependencies are installed in a virtual environment located at/tmp/pip-build-env-xxx
. This path is in thePYTHONPATH
of thesetup.py
file, but it is not passed to CMake and subsequent Python calls. This PR fixes this behavior by passing thePYTHONPATH
fromsetup.py
to CMake, and finally to themachete/generate.py
script (which usesjinja2
from build dependencies).