Zanie Blue
Zanie Blue
Thanks for the report! Sorry you ran into that — looks like something is mixed up. What version of uv are you using and what version worked? Related https://github.com/astral-sh/uv/issues/6661
Okay great good to know. We'll look into this.
If it's going to be processed downstream I think a JSON output format makes more sense than complicating the output. I'm pretty hesitant to add more columns to the table....
Seems kind of nice, but won't the paths be mostly redundant since they're all going to be in the same bin directory?
That might make more sense although we're calling the install directory the "uv tool directory" whereas the bin directory is the "tool executable directory". Maybe we need a toggle? Maybe...
I think `uv tool dir` should have a `--bin` flag that shows the binary directory instead? Regarding paths of tools, Cargo doesn't show them ``` ❯ cargo install --list -v...
I believe this is intentionally hidden, perhaps because it's only intended to be run once? I'm not sure.
Hi! Please see the [PEP 685](https://peps.python.org/pep-0685/#specification) specification which says: > When comparing extra names, tools MUST normalize the names being compared using the semantics outlined in [PEP 503](https://peps.python.org/pep-0503/#normalized-names) for names:...
Could you split up your examples a bit with some explanation of what each invocation is demonstrating? It's pretty hard to understand as-is.
@konstin could you check this resolves the issue on Linux please?