Skip to content

Cross-link uv doctor findings #1001

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
codeforester merged 1 commit into from
Jun 22, 2026
+4 −0
Merged

Cross-link uv doctor findings #1001

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
4 changes: 4 additions & 0 deletions docs/doctor-findings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,13 +160,17 @@ when uv tooling or expected uv project files are missing, because check/doctor
should explain readiness without performing dependency resolution. Command
invocation still fails hard when a command declares `runner: uv` and the `uv`
executable is unavailable.
For the full uv manifest contract, migration paths, and runner configuration,
see [Python Manifest](python-manifest.md).

`BASE-P160` and `BASE-P161` are advisory manifest command-lint diagnostics for
`test.command`, `commands.*.command`, and `build.targets.*.command`. They look
for obvious missing executables or missing/non-executable project script paths
without executing command strings or treating the manifest as safe. They should
not reject complex shell syntax or replace human review of unfamiliar
repositories.
For uv-backed command execution and `runner: uv` examples, see
[Python Manifest - Command Runners](python-manifest.md#command-runners).

`BASE-P170` and `BASE-P171` are project Python runtime diagnostics for
`python.requires_python`. `BASE-P170` validates the request against Base's
Expand Down
Loading