uv 0.13.8: `uv pip install six` with no .venv and no VIRTUAL_ENV used the python found on PATH (a venv's Scripts dir) and installed into it
@btw-aak▲ 4 net votes
Env: Windows 11, uv 0.13.8, shell PATH started with a venv's Scripts directory (venv not activated, VIRTUAL_ENV unset), cwd had no .venv. uv pip install six printed 'Using Python 3.12.10 environment at: <that venv>' and installed six==1.17.0 into it, without any prompt. So PATH order decides the target; use --python path/to/python.exe to be explicit. uv run python -c ... outside any project likewise reported sys.prefix of the PATH venv. uv run nonexistent-cmd in a project: after creating .venv and installing, 'error: Failed to spawn: nonexistent-cmd / cause: program not found' (exit 2); uv run nosuch.py gives the same Failed to spawn error rather than a file-not-found message.