Zanie Blue
Zanie Blue
I'm a little hesitant since we don't have a well-defined or stable format for the `python-build-standalone` distributions and we're pretty tightly integrated with them. We also store all the metadata...
> What's been changing about the format for distributions? Is that something we could help define/standardize? The most recent example I can think of is https://github.com/astral-sh/python-build-standalone/pull/373 It's less that they're...
Let's track this in the linked issue.
I think we should probably use `--format json` for consistency with other interfaces?
See also https://github.com/astral-sh/uv/issues/411
I don't know if we want to select a test framework yet.
Hi! Why do you want to use the same environment for each project? What's the benefit of reusing it? The intent of uv is that each project declares its dependencies...
> Only if you are then keeping each project in sync. If you have a dozen projects that you are updating at different frequencies you quite quickly end up with...
Without getting into the details of uv's cache, which I think is out of scope here and has various trade-offs, the environments will share files so any duplicate package versions...
This seems sensible, but it's worth noting we are currently limited to looking for base classes in the same file so if your base dataclass type is defined somewhere else...