-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Should uv sync
remove extraneous packages?
#4358
Comments
In brief, I think we should:
|
## Summary First step of #4358. `uv sync` will now remove any extraneous installations by default.
Currently |
I don't think they should always clean the virtual environment. I think it's too common for people to manually manage packages in Python and without an explicit sync it seems excessive for us to purge extraneous packages. Changing remove to be more clearly scoped by default seems like a more intuitive user experience. |
Does this mean: |
My current vote is that it uses the same semantics as |
IIUC, uv's top level commands do some automations to keep your workspace in sync between lockfile, pyproject.toml and venv. |
I think we made a decision on this — we have a toggle now. |
For anyone coming here after not finding the switch when looking at |
It currently does not, while
uv pip sync
does. This would also affect whetheruv remove
removes all extraneous packages, or has to do extra work to only remove the affected packages.The text was updated successfully, but these errors were encountered: