mirror of
https://github.com/astral-sh/uv.git
synced 2025-07-12 07:45:00 +00:00
34552e2d3d
## Summary It turns out that we were returning slightly different interpreter paths on repeated `uv run --with` commands. This likely didn't affect many (or any?) users, but it does affect our test suite, since in the test suite, we use a symlinked interpreter. The issue is that on first invocation, we create the virtual environment, and that returns the path to the `python` executable in the environment. On second invocation, we return the `python3` executable, since that gets priority during discovery. This on its own is potentially ok. The issue is that these resolve to different `sys._base_executable` values in these flows... The latter gets the correct value (since it's read from the `home` key), but the former gets the incorrect value (since it's just the `base_executable` of the executable that created the virtualenv, which is the symlink). We now use the same logic to determine the "cached interpreter" as in virtual environment creation, to ensure consistency between those paths. |
||
|---|---|---|
| .. | ||
| python | ||
| src | ||
| Cargo.toml | ||
| download-metadata.json | ||
| fetch-download-metadata.py | ||
| template-download-metadata.py | ||