mirror of https://github.com/astral-sh/uv
fb1d679f69
Previously, we'd use the `--reinstall` flag to determine if we should replace existing Python executables in the bin directory during an install. There are a few problems with this: - We replace executables we don't manage - We can replace executables from other uv Python installations during reinstall (surprising) - We don't do the "right" thing when installing patch versions e.g. installing `3.12.4` then `3.12.6` would fail without the reinstall flag In `uv tool`, we have separate `--force` and `--reinstall` concepts. Here we separate the flags (`--force` was previously just a `--reinstall` alias) and add inspection of the existing executables to inform a decision on replacement. In brief, we will: - Replace any executables with `--force` - Replace executables for the same installation with `--reinstall` - Replace executables for an older patch version by default |
||
|---|---|---|
| .. | ||
| .overrides | ||
| assets | ||
| concepts | ||
| configuration | ||
| getting-started | ||
| guides | ||
| js | ||
| pip | ||
| reference | ||
| stylesheets | ||
| .gitignore | ||
| index.md | ||
| requirements-insiders.in | ||
| requirements-insiders.txt | ||
| requirements.in | ||
| requirements.txt | ||