mirror of https://github.com/astral-sh/uv
2df06ebfbc
By default, `uv venv <venv-name>` currently removes the `<venv-name`> directory if it exists. This can be surprising behavior: not everyone expects an existing environment to be overwritten. This PR updates the default to fail if a non-empty `<venv-name>` directory already exists and neither `--allow-existing` nor the new `-c/--clear` option is provided (if a TTY is detected, it prompts first). If it's not a TTY, then uv will only warn and not fail for now — we'll make this an error in the future. I've also added a corresponding `UV_VENV_CLEAR` env var. I've chosen to use `--clear` instead of `--force` for this option because it is used by the `venv` module and `virtualenv` and will be familiar to users. I also think its meaning is clearer in this context than `--force` (which could plausibly mean force overwrite just the virtual environment files, which is what our current `--allow-existing` option does). Closes #1472. --------- Co-authored-by: Zanie Blue <contact@zanie.dev> |
||
|---|---|---|
| .. | ||
| build-binaries.yml | ||
| build-docker.yml | ||
| ci.yml | ||
| publish-docs.yml | ||
| publish-pypi.yml | ||
| release.yml | ||
| setup-dev-drive.ps1 | ||
| sync-python-releases.yml | ||