Sandu

There are drawbacks to doing this if you ever want to implement some sort of class hierarchy for your structs. A setter from a base class will return a base...

> What are the typical use-cases here? In my case it's a docker build in a github workflow. Caching docker layers on github runners is impossible AFAIK. Caching `~/.cache` is...

> I'm mostly wondering if it _has_ to be wheels or if we could just make it easy to pre-populate the uv cache. wheels are supported by standard `pip install`....

> I'm not sure how much we should go out of our way to support using pip to consume an output of uv? It seems weird to use uv in...

> I'm not a fan of expanding scope, so don't do that, but `rye add` can add deps, dev-deps, optional deps and excluded deps. Extending the pattern it seems like...

> lgtm. I can review, but note I'm just a contributor and can't do more in this repo. I don't think I can ask for reviewers. Your name was there...

> and dependencies B -> E and E -> F. With our current design, E can say `F = { workspace = true }` and we can figure out the...

> In this example `B` would have to make sure that both `E` and `F` are included in its workspace definition. After looking at the source a bit more I...

> They don't work well as a tool for sharing a library between two applications. That's true, but I think with a few tweaks they could provide a clean solution...

The [new PR](https://github.com/astral-sh/uv/pull/4610) provides explicit support for the use-case. It's a lot more straightforward from an end-user perspective, and interestingly didn't require the change from `.strip_prefix` to `relative_to`.