Zanie Blue
Zanie Blue
> But having said that, no Homebrew users had complained about the behaviour of virtualenv or venv until January of this year, suggesting that it can't be that common a...
Unfortunately macOS is still a major bottleneck in CI — but otherwise I'm supportive of this.
Also might be helpful for #5726
Yes, `uvx` does not install a tool by design — it uses an isolated environment.
(`uvx` is equivalent to `uv tool run` which is roughly equivalent to `pipx run` which also does not install the tool in your bin directory)
> This is especially useful for tools where you need the uvx --from flag, e.g. [pepotron](https://pypi.org/project/pepotron/) but don't if you uv tool install first, e.g. v tool run --from pepotron...
That's an interesting idea. Probably worth a try!
Hm. An export of the `pyproject.toml` constraints?
Does the error occur during `uv lock`? It seems likely the error is during _resolution_ in which we need to build the package to determine its metadata?
This was closed because the behavior is expected, we need to resolve all the dependencies — there's no evidence of incorrect _installation_ here.