Zanie Blue
Zanie Blue
~Needs validation on Windows and more explicit test coverage.~ @konstin tested this and I added a test with coverage
I presume not yeah.
@shaunhegarty can you share more about why `uv run` is not suitable for use in GitHub Actions in your use-case?
@gbdlin > for example with Docker used for local development with bind mount for project directory, virtualenv will be taken from the host instead of one built inside the docker...
@yasserfarouk Thanks for sharing. That's also discussed in #1495
@gbdlin I don't think this is true > Solution with anonymous mount for .venv directory causes a rebuild of virtualenv on first use of command with docker compose, as it...
> You can’t run something like uv add from a container. The same problem occurs when running some scripts that needs to write in to your project’s directory (for example...
I feel like it's this simple: ``` ❯ docker volume ls DRIVER VOLUME NAME ❯ docker run \ --rm \ --volume .:/app \ --volume /app/.venv \ --publish 8000:8000 \ -it...
@edmorley sort of. If I put on my pedantic hat, this is about configuring the path of the project's virtual environment and the other one is about allowing `uv sync`...
Sorry I'm not sure I follow. `uv lock --upgrade` or `uv sync --upgrade` is how you should upgrade to the latest version of a package (as supported by your constraints)....