-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Command uv pip sync requirements.txt
remove pip in venv create with uv venv --seed
#7121
Comments
I’ll take a look, we special-case this so pip shouldn’t be removed. |
I misremembered -- we preserve "seed" packages only if the virtualenv was created by a tool other than uv. |
Can uv keep "seed" packages if create venv by |
Yeah we probably should? I'm not sure why we wouldn't want to. |
+1 to never remove seed packages by default. I think wanting to sync them is more of an edge case than not wanting it. |
We'll need to track this state, presumably in the
|
Like, track the fact that we created the env with seed packages there? |
I can do that, not too hard. |
Version info (on macOS)
Content of requirements.in
Create venv
Generate requirements.txt
Run sync
The text was updated successfully, but these errors were encountered: