Zanie Blue

@memark did you do `UV_PROJECT_ENVIRONMENT=/usr/local/`?

We expect to receive a path to a Python environment, i.e., a directory which contains a Python environment. Generally, this is the path to a virtual environment e.g. ``` ❯...

You can also probably just get away with a virtual environment ``` uv sync export PATH="$(pwd)/.venv/bin:$PATH" ``` as demoed in https://github.com/astral-sh/uv-docker-example/blob/c16a61fb3e6ab568ac58d94b73a7d79594a5d570/Dockerfile#L25-L34 I don't think the virtual environment itself will add...

See https://github.com/astral-sh/uv/issues/12108#issuecomment-2715153717 Your shell is sending one SIGINT, uv is sending another.

Related to https://github.com/astral-sh/uv/issues/7803 We don't have a great recommendation here yet.

I understand the desire, but it seems like this is sort of something for the VSCode team to tackle. I don't understand the nuances of the debugger setup and if...

You can also get the path with `uv sync --script example.py --dry-run --output-format json | jq -r '.sync.environment.path'`

I think it's worth releasing the initial change regardless, it's a bug fix which I think takes precedence over the performance optimization here especially without benchmarks.

The `realpath` dependency may be a real problem on old macOS versions (e.g., https://github.com/astral-sh/uv/issues/9532#issuecomment-2514962865) but yeah I don't think that's a critical concern. Thanks for doing some benches @cipriancraciun. I...

I ran into another error when attempting to use `python -m venv`: ``` Run & (./uv python find 3.13t) -m venv .venv Error: Command '['D:\\a\\uv\\uv\\.venv\\Scripts\\python.exe', '-m', 'ensurepip', '--upgrade', '--default-pip']' returned...