From b27219174e25788ab270f2b06400536034c34e49 Mon Sep 17 00:00:00 2001 From: Johnny Greco Date: Tue, 7 Jul 2026 16:09:34 +0000 Subject: [PATCH] Generalize dependency export guidance Signed-off-by: Johnny Greco --- projects/python-project-template/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/projects/python-project-template/README.md b/projects/python-project-template/README.md index f8fc8e1a..d9cc5004 100644 --- a/projects/python-project-template/README.md +++ b/projects/python-project-template/README.md @@ -40,10 +40,10 @@ uv build Use `uv add ` for runtime dependencies and `uv add --dev ` for development tools. uv updates `pyproject.toml` and `uv.lock` together. -nSpect needs a resolved dependency manifest it can inspect. `uv.lock` remains -the source of truth for installs, while `requirements.txt` is a generated, -hash-pinned export of runtime dependencies for the scanner. Do not edit the -export by hand. Regenerate it after every runtime dependency update: +`uv.lock` remains the source of truth for installs. Keep `requirements.txt` as +a generated, hash-pinned export of runtime dependencies for compatibility with +workflows that consume requirements files. Do not edit the export by hand. +Regenerate it after every runtime dependency update: ```sh uv export \