Skip to content
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

Add a basic uv sync command #3432

Closed
charliermarsh opened this issue May 7, 2024 · 0 comments · Fixed by #3436
Closed

Add a basic uv sync command #3432

charliermarsh opened this issue May 7, 2024 · 0 comments · Fixed by #3436
Assignees
Labels
cli Related to the command line interface preview Experimental behavior

Comments

@charliermarsh
Copy link
Member

Let's sketch this out early so that we're forced to code-share with uv run.

@charliermarsh charliermarsh added cli Related to the command line interface preview Experimental behavior labels May 7, 2024
@charliermarsh charliermarsh self-assigned this May 7, 2024
charliermarsh added a commit that referenced this issue May 8, 2024
## Summary

These aren't intended for production use; instead, I'm just trying to
frame out the overall data flows and code-sharing for these commands. We
now have `uv sync` (sync the environment to match the lockfile, without
refreshing or resolving) and `uv lock` (generate the lockfile). Both
_require_ a virtual environment to exist (something we should change).
`uv sync`, `uv run`, and `uv lock` all share code for the underlying
subroutines (resolution and installation), so the commands themselves
are relatively small (~100 lines) and mostly consist of reading
arguments and such.

`uv lock` and `uv sync` don't actually really work yet, because we have
no way to include the project itself in the lockfile (that's a TODO in
the lockfile implementation).

Closes #3432.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Related to the command line interface preview Experimental behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant