Zanie Blue
Zanie Blue
Sort of a hack, but we could special case `--python-version requires-python` 🤔
Because `pip` does not read metadata from the `pyproject.toml` (as a design goal) and reading that metadata implicitly in a "compatible" interface would be surprising to some users.
We're intending to address bulk operations some other way e.g. `uv tool upgrade --all`. I wouldn't mind adding a `--no-show-executables` flag though; similar to how we just added a `--show-paths`...
Note I think you can also do `uv tool install --upgrade` and skip the `uninstall`?
Yeah idk, `--no-show-executables` and `--no-show-versions?`. Eventually it just makes sense to create a JSON output format.
Note: You can't pass the `--preview` flag to `ipython`. `uv internal error` is coming from the trampoline https://github.com/astral-sh/uv/blob/2cd63f06dc8139adafdabfcbeda1a4250d4c0238/crates/uv-trampoline/src/bounce.rs#L472 and the error is from https://github.com/astral-sh/uv/blob/2cd63f06dc8139adafdabfcbeda1a4250d4c0238/crates/uv-trampoline/src/bounce.rs#L299-L318 cc @konstin and @samypr100
Thanks! cc @charliermarsh might a regression from #5888
This sounds cool as a `uv export` format option. I don't think it's on our immediate roadmap though.
> (Could a reverse uv import option that takes an SBOM to set up a project/venv also be useful?) Yeah this would also be cool, but would need quite a...
I'm fine with dropping the json qualifier though I think we should allow it