Skip to content

Generalize dependency export guidance #9

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
johnnygreco merged 1 commit into from
Jul 7, 2026
Merged

Generalize dependency export guidance #9

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
8 changes: 4 additions & 4 deletions projects/python-project-template/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,10 @@ uv build
Use `uv add <package>` for runtime dependencies and `uv add --dev <package>` 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 \
Expand Down