fix(python plugin): set UV_PYTHON to python in .venv #2478
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.
Fixes #2411
Summary
The UV_PYTHON env variables sets which python executable uv will use.
The current plugin sets the UV_PYTHON value to
.devbox/nix/profile/default/bin/python
which meansuv pip install
commands will try to install and save libraries under the.devbox/nix/profile/default/lib/python3.x/site-packages
directory.This will cause an error as the directory doesn't have write permissions because it exists under a folder that is a symlinked to a folder under the
/nix/store
path.This change makes sure UV_PYTHON points to the python executable under .venv.
This will make
uv pip install
commands install libraries to the site-packages directory under .venv just like normalpip install
would.How was it tested?