Zanie Blue
Zanie Blue
Possibility for no output when running a script with `uv run main.py` (that has filled requirements)
It seems generally helpful to understand that your invocation is going to run in an entirely different environment than other `uv run` requests. What's the problem with the output?
Yes we added the builds yesterday. I ran the action and it updated https://github.com/astral-sh/rye/pull/1406 — if you want to build that branch and test things out to make sure it...
Is this a problem of the standalone builds? i.e., is this reproducible with a local build with `pyenv`? I wonder if this is just a difference in how the certificates...
Regarding installing something before syncing, you could do something like this? ``` uv venv uv pip install uv sync --frozen --inexact ```
Well, you'll need to export it if you want the version to come from the lockfile. We're also considering adding an `--only-install-package` in the same way as we have `--no-install-package`.
`uv pip install ` won't install the version of `package` defined in your lockfile, if any. `uv sync --frozen --inexact` will respect your lockfile yes, it just won't remove extraneous...
Thanks for the report! @konstin you marked this as an enhancement, is this not a bug? cc @charliermarsh
Thanks for the additional context. Is this hard?
There actually is since https://github.com/astral-sh/uv/pull/6210 — we need to update the documentation to clarify this.
I don't fully understand what this means. I worry how close the flag is to `--no-editable`.