From bc788653a39e263a2ec94da92d1370519e00b752 Mon Sep 17 00:00:00 2001 From: Zanie Blue Date: Wed, 9 Apr 2025 17:22:17 -0500 Subject: [PATCH] Fix lockfile note --- docs/concepts/projects/layout.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/concepts/projects/layout.md b/docs/concepts/projects/layout.md index ffbd03467ab9d..c8444bd4224c0 100644 --- a/docs/concepts/projects/layout.md +++ b/docs/concepts/projects/layout.md @@ -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 @@ -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).