Monorepos: Replicating nx affected, nx run-many with uv.

[gregglind]

Summary

nx affected promises to "run only tasks affected by a PR".

Having uv tree and uv lock --check makes me wonder if uv could replace this command?

If this is out of scope for uv proper, is there a suggested better tool or pattern?

Context

Non-workspace monorepos, where each project is pytest testable, but there is a root pyproject to oversee and enforce code patterns (ruff, etc), python versions, and other shared contraints.

Example

No response

[zanieb]

We're interested in this, but we're far out from implementing it in a robust way.

The most relevant work here is astral-sh/ruff#13402 which is used by some people for test selection.

[gregglind]

Thanks for sharing that link and validating the desire.

Even "non-robust" ways (packages with source lines in the lockfile, assuming they are all in projects with a pyproject.toml) are a great starting point!

[gregglind]

Further amplification: a place where UV can add value (the "most missing piece") is by exposing more of the dependency graph, either as part of lock or tree. This is orthogonal to the discussion in #5903.

Building a run-many task runner that uses that information might be a simple as calling uv run --project or uv run --directory for each line in that graph (bottom-up).

In particular, listing every pyproject.toml that would be involved in a particular uv lock scenario would be very helpful, and strictly better than grep.

uv -v lock --dry-run |& grep static has lines like

DEBUG Found static `pyproject.toml` for: my-lib @ file:///Users/glind/some/monorepo/path`