Skip to content

Fix lockfile note #12793

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 10, 2025
Merged

Fix lockfile note #12793

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions docs/concepts/projects/layout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,9 +79,8 @@ The lockfile is [automatically created and updated](./sync.md#automatic-lock-and
invocations that use the project environment, i.e., `uv sync` and `uv run`. The lockfile may also be
explicitly updated using `uv lock`.

`uv.lock` is a human-readable TOML file but is managed by uv and should not be edited manually.
There is no Python standard for lockfiles at this time, so the format of this file is specific to uv
and not usable by other tools.
`uv.lock` is a human-readable TOML file but is managed by uv and should not be edited manually. The
`uv.lock` format is specific to uv and not usable by other tools.

!!! note

Expand All @@ -90,7 +89,6 @@ and not usable by other tools.

Some of uv's functionality cannot be expressed in the `pylock.toml` format,
so uv will continue to use the `uv.lock` format.
The `uv.lock` format is specific to uv and not usable by other tools.

However, support for `pylock.toml` is planned everywhere uv currently supports `requirements.txt` files.
For more details and updates on progress, see [12584](https://github.com/astral-sh/uv/issues/12641).
Loading