Zanie Blue
Zanie Blue
`UV_PYTHON_INSTALL_DIR` is where we install Python versions — we don't know how to read pyenv's structure.
We're not willing to read folder structures defined by other tools. I'd recommend placing those directories on the `PATH` if you want us to discover interpreters in them.
Thanks for the report. Can you use SSH credentials instead of HTTPS? Or authenticate prior to the command and use a [Git credential store](https://git-scm.com/docs/git-credential-store)? Our supported authentication schemes are discussed...
Thanks for the detailed description! I don't see a particular value in mirroring `pipx` closely, we already have `uv tool` which roughly mirrors this with `uv tool run` and `uv...
> uv breaks that mental model by copying a package manager from a different ecosystem. To be clear, we didn't copy this other package manager. We assessed interfaces like this...
Including the root project, I presume? `--only-dev` for consistency with `--with` and `--no-install`?
I feel like `--prod` might imply something more, like ignoring "sources"?
Yep, the legacy one. I don't mind using it for builds in general, but I think we need to provide a better experience than it delivers to people who just...
Yes it's not quite a specification violation, but we strive to conform with "SHOULD" too
As of [uv 0.4.0](https://github.com/astral-sh/uv/releases/tag/0.4.0), we no longer build the package if a build system is not defined unless the user opts-in.