-
Notifications
You must be signed in to change notification settings - Fork 760
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
Deprecate the --isolated
flag
#5466
Conversation
c7eb248
to
36b2f4d
Compare
Could you also update the |
Yes, thanks for the reminder. |
36b2f4d
to
e3ccd31
Compare
e1412c5
to
1b4d926
Compare
e3ccd31
to
5e77e2c
Compare
1b4d926
to
a9560ea
Compare
5e77e2c
to
905aa85
Compare
383b43d
to
99638ad
Compare
2bf70cc
to
abf2d17
Compare
## Summary This PR gets rid of the global `--isolated` flag (which serves a bunch of independent responsibilities right now) on `uv tool run` in favor of a dedicated `--isolated` flag, which tells uv to avoid re-using an existing tool environment for this invocation. We'll add the same thing to `uv run`, to avoid using the base project environment. This will become a bit clearer in #5466, when we deprecate the `--isolated` flag on the preview APIs.
99638ad
to
608a4cf
Compare
73105e2
to
2879fde
Compare
Will review this next. |
Oh I was just gonna merge -- go for it, np. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thought the review request was new for some reason :)
2879fde
to
ef16250
Compare
ef16250
to
7b02c18
Compare
Summary
This PR deprecates the
--isolated
flag. The treatment varies across the APIs:--no-config
.tool run
andrun
specifically, we don't even warn, because we can't differentiate the command-specific--isolated
from the global--isolated
.