-
Notifications
You must be signed in to change notification settings - Fork 721
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
--no-build-isolation
isn't supported for uv tool
#6083
Comments
Marking as a bug since I assumed it did work. |
Hm this is tough, it seems really weird to detect a virtual environment when installing a tool? |
Note that this is just the environment used for building. It doesn't need to have access to the virtualenv after the build step. |
I guess we can change interpreter lookup when |
This might be tricky, we always create a virtualenv for the tool and install into the virtualenv. We'd need to find a way to... give that environment access to the user-provided virtualenv, I think? Like via |
I think the use of
OnlySystem
for Python discovery means that users can't provide a pre-populated environment for (e.g.) PyTorch.See, e.g., #1715 (comment).
The text was updated successfully, but these errors were encountered: