Zanie Blue
Zanie Blue
@bjornasm I'm not quite sure what you're looking for, but `uv venv && uv pip sync requirements.txt` or `uv sync` (for `uv.lock`)
The lockfile will never be used to update the `pyproject.toml`, the `pyproject.toml` is the source of truth of your dependencies. The `uv.lock` captures exactly which versions of your dependencies will...
Yeah we don't support this yet, but we plan to in some way.
@Mai0313 please don't ask for updates. See #9452. This issue is being tracked in #5903
As a workaround, I use this in my project: ``` sed -i -e "s/0.0.0/${GITHUB_REF#refs/*/}/" pyproject.toml ``` https://github.com/astral-sh/packse/blob/70abfe8f64a9746452c02cb514942f879c7eaccc/.github/workflows/release.yaml#L34-L36
The `uv version` command already exists, so I need to come up with a design to either phase that out in favor this functionality or choose a new command name....
@sam57719 that doesn't mean it's not a breaking change to switch the functionality. There is downstream code that _will_ break if we change it.
Thanks for engaging on the design! I think that `uv project` might be weird since all the other "project" commands are top-level, e.g., `init`, `sync`, `lock` are all project operations.
Retitled to try to improve discoverability. We get a lot of duplicates of this one.
I think `file://` for MIRROR is probably the move here?