Also, should we add an entry to the preview docs?

Thanks!

I'd go for a single API for machine-readable workspace metadata, I'd have expected this to print something more like a uv pip list table with names and paths.

If we're worried about stabilizing uv workspace metadata, we can stabilize a v1.0 with only workspace member information, and have a v1.1 that populates more fields behind --preview.

I'd have expected this to print something more like a uv pip list table with names and paths.

I'm not really into displaying tables. I think I'd expect you to pass items from here to uv workspace dir --package <name> if you want to do this simple composition.

Here I'm mostly thinking of the trivial case where you want to loop over workspace members. I don't want to make people use jq for that?

When do you need to iterate over workspace members?

e.g., I need to run pytest / pyright / deptry in each workspace member

Does that mean uv workspace will be entirely a primarily machine-readable interface, and human readable output will go into uv tree(?) or another interface?

I'm not sure yet. I just don't think showing the paths in this specific command is worth the added complexity, since they're usually just a bunch of directories next to each other and it breaks composability.

We should pin down whether we want this interface to be specifically machine readable (with a specific format) or not, otherwise it will be hard to change it later. If we want it to be shell-iterable, we should commit to printing a single name per line and document that format.

If we want it to be shell-iterable, we should commit to printing a single name per line and document that format.

That's what I want to do here, I'm not sure why we need to document that explicitly? but I can do so. The command is just in preview though, I'm looking for concrete use-cases and feedback to guide the interface of this and the entire workspace namespace.

I really mean just something simple in the docs:

The output is one package name per line.

And maybe an even more explicit:

This interface is machine readable.

As long as it's in preview we can change it again anyway.