Improve error message when a virtual environment Python symlink is broken #12168

konstin · 2025-03-14T14:02:27Z

When removing a Python interpreter underneath an existing venv, uv currently shows a not found error:

error: Failed to inspect Python interpreter from active virtual environment at `.venv/bin/python3`
  Caused by: Python interpreter not found at `/home/konsti/projects/uv/.venv/bin/python3`

This is unintuitive, as the file for the Python interpreter does exist, it is a broken symlink that needs to be replaced with uv venv.

I've been encountering those occasionally, and I expect users that switch between versions a lot will, too, especially when they also use pyenv or a similar Python manager.

The new error hints at this solution:

error: Failed to inspect Python interpreter from active virtual environment at `.venv/bin/python3`
  Caused by: Broken symlink at `.venv/bin/python3`, was the underlying Python interpreter removed?

hint: To recreate the virtual environment, run `uv venv`

charliermarsh · 2025-03-14T14:08:57Z

Nice. Can we add another newline before the hint, and remove the trailing period on the hint per the style guide?

konstin · 2025-03-14T14:18:42Z

I'm considering removing InterpreterError::NotFound, do we have cases we want to permit that are not covered by InterpreterError::BrokenSymlink?

zanieb · 2025-04-16T16:44:44Z

I'm considering removing InterpreterError::NotFound

I think we need it for a case like uv run -p /path/to/python3.12, right? A missing file there is different than a broken symlink

zanieb · 2025-04-16T16:45:56Z

crates/uv-python/src/discovery.rs

-                        python_preference: preference,
-                        environment_preference: environments,
-                    })),
+                    Err(InterpreterError::NotFound(_) | InterpreterError::BrokenSymlink(_)) => {


Isn't it important to report the broken symlink in this context too? I'm not sure how that'd look downstream. You could test with uv venv foo && <uninstall python> && uv run -p foo?

I guess the hint could be wrong here if it's not a virtual environment?

For this case, I get the same behavior with and without this PR:

$ uv venv botched && rm botched/bin/python && ln -s /does/not/exist/python botched/bin/python && uv run -p botched Using CPython 3.13.2 Creating virtual environment at: botched Activate with: source botched/bin/activate error: No interpreter found for directory `botched` in virtual environments, managed installations, or search path $ uv-pr venv botched && rm botched/bin/python && ln -s /does/not/exist/python botched/bin/python && uv-pr run -p botched Using CPython 3.13.2 Creating virtual environment at: botched Activate with: source botched/bin/activate error: No interpreter found for directory `botched` in virtual environments, managed installations, or search path

The error is imo misleading, we found an interpreter, but it's broken, though that looks like a different problem.

zanieb · 2025-04-16T16:48:48Z

crates/uv/tests/it/pip_compile.rs

+    error: Failed to inspect Python interpreter from active virtual environment at `.venv/bin/python3`
+      Caused by: Broken symlink at `.venv/bin/python3`, was the underlying Python interpreter removed?
+
+    hint: To recreate the virtual environment, run `uv venv`


What if the virtual environment was found in a parent directory or specified some other way? I'm worried this hint might be misleading.

Should we make the hint more generic, like "hint: The Python interpreter seems to have been uninstalled, consider recreating the virtual environment"?

That seems more correct. You could sniff for pyenv.cfg too? If this was handled in the caller instead (as it sort of was before this PR?) you would have information about whether it's a virtual environment or not?

@jtfmumm you got an opinion on that from the other work on healing broken venvs wrt pyvenv.cfg?

i.e., we have

uv/crates/uv-python/src/discovery.rs

Lines 819 to 828 in 7d12b6a

// If the interpreter is from an active, valid virtual environment, we should

// fail because it's broken

if let Some(Ok(true)) = matches!(source, PythonSource::ActiveEnvironment)

.then(|| {

path.parent()

.and_then(Path::parent)

.map(|path| path.join("pyvenv.cfg").try_exists())

})

.flatten()

{

konstin · 2025-04-16T22:32:17Z

I'm considering removing InterpreterError::NotFound

I think we need it for a case like uv run -p /path/to/python3.12, right? A missing file there is different than a broken symlink

I'm afraid I'm not following along what /path/to/python3.12 means. If I do uv run -p /usr/bin/python3.12 python it works in either case. If I do uv run -p /does/not/exist/python3.12 python there's the current behavior and the one if we remove InterpreterError::NotFound.

Current behavior:

$ uv run -p /does/not/exist/python3.12 python
error: No interpreter found for path `/does/not/exist/python3.12` in virtual environments, managed installations, or search path

After removing InterpreterError::NotFound:

$ uv run -p /does/not/exist/python3.12 python
error: Failed to inspect Python interpreter from provided path at `/does/not/exist/python3.12`
  Caused by: Failed to query Python interpreter
  Caused by: failed to canonicalize path `/does/not/exist/python3.12`: No such file or directory (os error 2)

zanieb · 2025-04-16T22:39:04Z

I see. I think that might cause other problems for discovery, I'd need to look carefully at the downstream effects. I can do that though..

konstin · 2025-04-16T22:55:50Z

It would be interesting to know if this has downstream effects, it would be nice if we could scope the special case down to only broken symlinks, which tightly corresponds to uninstalled python interpreters.

konstin · 2025-05-06T11:20:47Z

@zanieb Could you find out if we still need InterpreterError::NotFound with InterpreterError::BrokenSymlink, or if there are downstream problems?

zanieb · 2025-05-06T12:27:34Z

I can try, but it's going to be hard to find time as it's not very critical. Do we need to remove it? It's kind of high risk to remove error variants that are used in Python discovery.

konstin · 2025-05-06T14:03:43Z

If we don't have the clarity about InterpreterError::NotFound, can we move ahead with just adding InterpreterError::BrokenSymlink?

When removing a Python interpreter underneath an existing venv, uv currently shows a not found error: ``` error: Failed to inspect Python interpreter from active virtual environment at `.venv/bin/python3` Caused by: Python interpreter not found at `/home/konsti/projects/uv/.venv/bin/python3` ``` This is unintuitive, as the file for the Python interpreter does exist, it is a broken symlink that needs to be replaced with `uv venv`. The new error hints at this solution: ``` error: Failed to inspect Python interpreter from active virtual environment at `.venv/bin/python3` Caused by: Broken symlink at `.venv/bin/python3`, was the underlying Python interpreter removed? hint: To recreate the virtual environment, run `uv venv`. ```

zanieb · 2025-05-07T17:28:38Z

crates/uv-python/src/interpreter.rs

+        ":".bold(),
+        "uv venv".green(),
+    )]
+    BrokenVenvSymlink(PathBuf),


Doesn't specializing this case mean we're not improving the error message when it's not a virtual environment? I'm curious why you chose this instead of having conditional display of the hint? Either with BrokenSymlink(PathBuf, bool) or by deferring that pyvenv.cfg lookup to error display time. (adding another dedicated variant is an option, of course, but seems like more work downstream of here)

I've only seen the error show in uv for venvs, but it doesn't hurt to cover the non-venv case, too.

In the test the error looks suboptimal too (we're ignoring the explicitly passed python interpreter is unexpected, I checked both uv venv and uv pip compile), but that's a different problem (and the behavior for this case does not change).

zanieb · 2025-05-07T17:58:51Z

Thanks for your patience

zanieb · 2025-05-07T18:06:05Z

crates/uv/tests/it/pip_compile.rs

+    ----- stdout -----
+
+    ----- stderr -----
+      × No interpreter found for path `python3.14159` in managed installations or search path


The specialization for that would be at

uv/crates/uv-python/src/discovery.rs

Lines 897 to 906 in 060be9c

Err(InterpreterError::NotFound(_)) => Ok(Err(PythonNotFound {

request: request.clone(),

python_preference: preference,

environment_preference: environments,

})),

Err(err) => Err(Error::Query(

Box::new(err),

path.clone(),

PythonSource::ProvidedPath,

)),

It's not great right now. I think we should tackle that separately though.

Looking at an aspect of this briefly... #13335

e.g., these are misleading cruft in the error message at #12168 (comment) ``` ❯ uv python find /foo/bar error: No interpreter found for path `/foo/bar` in virtual environments, managed installations, or search path ❯ cargo run -q -- python find /foo/bar error: No interpreter found at path `/foo/bar` ```

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [astral-sh/uv](https://github.com/astral-sh/uv) | minor | `0.6.16` -> `0.7.3` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>astral-sh/uv (astral-sh/uv)</summary> ### [`v0.7.3`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#073) [Compare Source](astral-sh/uv@0.7.2...0.7.3) ##### Enhancements - Add `--dry-run` support to `uv self update` ([#9829](astral-sh/uv#9829)) - Add `--show-with` to `uv tool list` to list packages included by `--with` ([#13264](astral-sh/uv#13264)) - De-duplicate fetched index URLs ([#13205](astral-sh/uv#13205)) - Support more zip compression formats: bzip2, lzma, xz, zstd ([#13285](astral-sh/uv#13285)) - Add support for downloading GraalPy ([#13172](astral-sh/uv#13172)) - Improve error message when a virtual environment Python symlink is broken ([#12168](astral-sh/uv#12168)) - Use `fs_err` for paths in symlinking errors ([#13303](astral-sh/uv#13303)) - Minify and embed managed Python JSON at compile time ([#12967](astral-sh/uv#12967)) ##### Preview features - Build backend: Make preview default and add configuration docs ([#12804](astral-sh/uv#12804)) - Build backend: Allow escaping in globs ([#13313](astral-sh/uv#13313)) - Build backend: Make builds reproducible across operating systems ([#13171](astral-sh/uv#13171)) ##### Configuration - Add `python-downloads-json-url` option for `uv.toml` to configure custom Python installations via JSON URL ([#12974](astral-sh/uv#12974)) ##### Bug fixes - Check nested IO errors for retries ([#13260](astral-sh/uv#13260)) - Accept `musllinux_1_0` as a valid platform tag ([#13289](astral-sh/uv#13289)) - Fix discovery of pre-release managed Python versions in range requests ([#13330](astral-sh/uv#13330)) - Respect locked script preferences in `uv run --with` ([#13283](astral-sh/uv#13283)) - Retry streaming downloads on broken pipe errors ([#13281](astral-sh/uv#13281)) - Treat already-installed base environment packages as preferences in `uv run --with` ([#13284](astral-sh/uv#13284)) - Avoid enumerating sources in errors for path Python requests ([#13335](astral-sh/uv#13335)) - Avoid re-creating virtual environment with `--no-sync` ([#13287](astral-sh/uv#13287)) ##### Documentation - Remove outdated description of index strategy ([#13326](astral-sh/uv#13326)) - Update "Viewing the version" docs ([#13241](astral-sh/uv#13241)) ### [`v0.7.2`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#072) [Compare Source](astral-sh/uv@0.7.1...0.7.2) ##### Enhancements - Improve trace log for retryable errors ([#13228](astral-sh/uv#13228)) - Use "error" instead of "warning" for self-update message ([#13229](astral-sh/uv#13229)) - Error when `uv version` is used with project-specific flags but no project is found ([#13203](astral-sh/uv#13203)) ##### Bug fixes - Fix incorrect virtual environment invalidation for pre-release Python versions ([#13234](astral-sh/uv#13234)) - Fix patching of `clang` in managed Python sysconfig ([#13237](astral-sh/uv#13237)) - Respect `--project` in `uv version` ([#13230](astral-sh/uv#13230)) ### [`v0.7.1`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#071) [Compare Source](astral-sh/uv@0.7.0...0.7.1) ##### Enhancement - Add support for BLAKE2b-256 ([#13204](astral-sh/uv#13204)) ##### Bugfix - Revert fix handling of authentication when encountering redirects ([#13215](astral-sh/uv#13215)) ### [`v0.7.0`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#070) [Compare Source](astral-sh/uv@0.6.17...0.7.0) This release contains various changes that improve correctness and user experience, but could break some workflows; many changes have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes. ##### Breaking changes - **Update `uv version` to display and update project versions ([#12349](astral-sh/uv#12349 Previously, `uv version` displayed uv's version. Now, `uv version` will display or update the project's version. This interface was [heavily requested](astral-sh/uv#6298) and, after much consideration, we decided that transitioning the top-level command was the best option. Here's a brief example: ```console $ uv init example Initialized project `example` at `./example` $ cd example $ uv version example 0.1.0 $ uv version --bump major example 0.1.0 => 1.0.0 $ uv version --short 1.0.0 ``` If used outside of a project, uv will fallback to showing its own version still: ```console $ uv version warning: failed to read project: No `pyproject.toml` found in current directory or any parent directory running `uv self version` for compatibility with old `uv version` command. this fallback will be removed soon, pass `--preview` to make this an error. uv 0.7.0 (4433f41c9 2025-04-29) ``` As described in the warning, `--preview` can be used to error instead: ```console $ uv version --preview error: No `pyproject.toml` found in current directory or any parent directory ``` The previous functionality of `uv version` was moved to `uv self version`. - **Avoid fallback to subsequent indexes on authentication failure ([#12805](astral-sh/uv#12805 When using the `first-index` strategy (the default), uv will stop searching indexes for a package once it is found on a single index. Previously, uv considered a package as "missing" from an index during authentication failures, such as an HTTP 401 or HTTP 403 (normally, missing packages are represented by an HTTP 404). This behavior was motivated by unusual responses from some package indexes, but reduces the safety of uv's index strategy when authentication fails. Now, uv will consider an authentication failure as a stop-point when searching for a package across indexes. The `index.ignore-error-codes` option can be used to recover the existing behavior, e.g.: ```toml [[tool.uv.index]] name = "pytorch" url = "https://download.pytorch.org/whl/cpu" ignore-error-codes = [401, 403] ``` Since PyTorch's indexes always return a HTTP 403 for missing packages, uv special-cases indexes on the `pytorch.org` domain to ignore that error code by default. - **Require the command in `uvx <name>` to be available in the Python environment ([#11603](astral-sh/uv#11603 Previously, `uvx` would attempt to execute a command even if it was not provided by a Python package. For example, if we presume `foo` is an empty Python package which provides no command, `uvx foo` would invoke the `foo` command on the `PATH` (if present). Now, uv will error early if the `foo` executable is not provided by the requested Python package. This check is not enforced when `--from` is used, so patterns like `uvx --from foo bash -c "..."` are still valid. uv also still allows `uvx foo` where the `foo` executable is provided by a dependency of `foo` instead of `foo` itself, as this is fairly common for packages which depend on a dedicated package for their command-line interface. - **Use index URL instead of package URL for keyring credential lookups ([#12651](astral-sh/uv#12651 When determining credentials for querying a package URL, uv previously sent the full URL to the `keyring` command. However, some keyring plugins expect to receive the *index URL* (which is usually a parent of the package URL). Now, uv requests credentials for the index URL instead. This behavior matches `pip`. - **Remove `--version` from subcommands ([#13108](astral-sh/uv#13108 Previously, uv allowed the `--version` flag on arbitrary subcommands, e.g., `uv run --version`. However, the `--version` flag is useful for other operations since uv is a package manager. Consequently, we've removed the `--version` flag from subcommands — it is only available as `uv --version`. - **Omit Python 3.7 downloads from managed versions ([#13022](astral-sh/uv#13022 Python 3.7 is EOL and not formally supported by uv; however, Python 3.7 was previously available for download on a subset of platforms. - **Reject non-PEP 751 TOML files in install, compile, and export commands ([#13120](astral-sh/uv#13120), [#13119](astral-sh/uv#13119 Previously, uv treated arbitrary `.toml` files passed to commands (e.g., `uv pip install -r foo.toml` or `uv pip compile -o foo.toml`) as `requirements.txt`-formatted files. Now, uv will error instead. If using PEP 751 lockfiles, use the standardized format for custom names instead, e.g., `pylock.foo.toml`. - **Ignore arbitrary Python requests in version files ([#12909](astral-sh/uv#12909 uv allows arbitrary strings to be used for Python version requests, in which they are treated as an executable name to search for in the `PATH`. However, using this form of request in `.python-version` files is non-standard and conflicts with `pyenv-virtualenv` which writes environment names to `.python-version` files. In this release, uv will now ignore requests that are arbitrary strings when found in `.python-version` files. - **Error on unknown dependency object specifiers ([12811](astral-sh/uv#12811 The `[dependency-groups]` entries can include "object specifiers", e.g. `set-phasers-to = ...` in: ```toml [dependency-groups] foo = ["pyparsing"] bar = [{set-phasers-to = "stun"}] ``` However, the only current spec-compliant object specifier is `include-group`. Previously, uv would ignore unknown object specifiers. Now, uv will error. - **Make `--frozen` and `--no-sources` conflicting options ([#12671](astral-sh/uv#12671 Using `--no-sources` always requires a new resolution and `--frozen` will always fail when used with it. Now, this conflict is encoded in the CLI options for clarity. - **Treat empty `UV_PYTHON_INSTALL_DIR` and `UV_TOOL_DIR` as unset ([#12907](astral-sh/uv#12907), [#12905](astral-sh/uv#12905 Previously, these variables were treated as set to the current working directory when set to an empty string. Now, uv will ignore these variables when empty. This matches uv's behavior for other environment variables which configure directories. ##### Enhancements - Disallow mixing requirements across PyTorch indexes ([#13179](astral-sh/uv#13179)) - Add optional managed Python archive download cache ([#12175](astral-sh/uv#12175)) - Add `poetry-core` as a `uv init` build backend option ([#12781](astral-sh/uv#12781)) - Show tag hints when failing to find a compatible wheel in `pylock.toml` ([#13136](astral-sh/uv#13136)) - Report Python versions in `pyvenv.cfg` version mismatch ([#13027](astral-sh/uv#13027)) ##### Bug fixes - Avoid erroring on omitted wheel-only packages in `pylock.toml` ([#13132](astral-sh/uv#13132)) - Fix display name for `uvx --version` ([#13109](astral-sh/uv#13109)) - Restore handling of authentication when encountering redirects ([#13050](astral-sh/uv#13050)) - Respect build options (`--no-binary` et al) in `pylock.toml` ([#13134](astral-sh/uv#13134)) - Use `upload-time` rather than `upload_time` in `uv.lock` ([#13176](astral-sh/uv#13176)) ##### Documentation - Changed `fish` completions append `>>` to overwrite `>` ([#13130](astral-sh/uv#13130)) - Add `pylock.toml` mentions where relevant ([#13115](astral-sh/uv#13115)) - Add ROCm example to the PyTorch guide ([#13200](astral-sh/uv#13200)) - Upgrade PyTorch guide to CUDA 12.8 and PyTorch 2.7 ([#13199](astral-sh/uv#13199)) ### [`v0.6.17`](https://github.com/astral-sh/uv/releases/tag/0.6.17) [Compare Source](astral-sh/uv@0.6.16...0.6.17) #### Release Notes ##### Preview features - Add PyTorch v2.7.0 to GPU backend ([#13072](astral-sh/uv#13072)) ##### Bug fixes - Avoid panic for invalid Python versions ([#13077](astral-sh/uv#13077)) - Block scripts from overwriting `python` ([#13051](astral-sh/uv#13051)) - Check distribution names to handle invalid redirects ([#12917](astral-sh/uv#12917)) - Check for mismatched package and distribution names on resolver thread ([#13088](astral-sh/uv#13088)) - Fix panic with invalid last character in PEP 508 name ([#13105](astral-sh/uv#13105)) - Reject `requires-python` even if not listed on the index page ([#13086](astral-sh/uv#13086)) #### Install uv 0.6.17 ##### Install prebuilt binaries via shell script ```sh curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.6.17/uv-installer.sh | sh ``` ##### Install prebuilt binaries via powershell script ```sh powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.6.17/uv-installer.ps1 | iex" ``` #### Download uv 0.6.17 | File | Platform | Checksum | |--------|----------|----------| | [uv-aarch64-apple-darwin.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-apple-darwin.tar.gz) | Apple Silicon macOS | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-apple-darwin.tar.gz.sha256) | | [uv-x86\_64-apple-darwin.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-apple-darwin.tar.gz) | Intel macOS | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-apple-darwin.tar.gz.sha256) | | [uv-aarch64-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-pc-windows-msvc.zip) | ARM64 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-pc-windows-msvc.zip.sha256) | | [uv-i686-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-pc-windows-msvc.zip) | x86 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-pc-windows-msvc.zip.sha256) | | [uv-x86\_64-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-pc-windows-msvc.zip) | x64 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-pc-windows-msvc.zip.sha256) | | [uv-aarch64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-gnu.tar.gz) | ARM64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-gnu.tar.gz.sha256) | | [uv-i686-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-gnu.tar.gz) | x86 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-gnu.tar.gz.sha256) | | [uv-powerpc64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64-unknown-linux-gnu.tar.gz) | PPC64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64-unknown-linux-gnu.tar.gz.sha256) | | [uv-powerpc64le-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64le-unknown-linux-gnu.tar.gz) | PPC64LE Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64le-unknown-linux-gnu.tar.gz.sha256) | | [uv-s390x-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-s390x-unknown-linux-gnu.tar.gz) | S390x Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-s390x-unknown-linux-gnu.tar.gz.sha256) | | [uv-x86\_64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-gnu.tar.gz) | x64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-gnu.tar.gz.sha256) | | [uv-armv7-unknown-linux-gnueabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-gnueabihf.tar.gz) | ARMv7 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-gnueabihf.tar.gz.sha256) | | [uv-aarch64-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-musl.tar.gz) | ARM64 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-musl.tar.gz.sha256) | | [uv-i686-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-musl.tar.gz) | x86 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-musl.tar.gz.sha256) | | [uv-x86\_64-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-musl.tar.gz) | x64 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-musl.tar.gz.sha256) | | [uv-arm-unknown-linux-musleabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-arm-unknown-linux-musleabihf.tar.gz) | ARMv6 MUSL Linux (Hardfloat) | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-arm-unknown-linux-musleabihf.tar.gz.sha256) | | [uv-armv7-unknown-linux-musleabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-musleabihf.tar.gz) | ARMv7 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-musleabihf.tar.gz.sha256) | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

## 0.7.3 ### Enhancements - Add `--dry-run` support to `uv self update` ([#9829](astral-sh/uv#9829)) - Add `--show-with` to `uv tool list` to list packages included by `--with` ([#13264](astral-sh/uv#13264)) - De-duplicate fetched index URLs ([#13205](astral-sh/uv#13205)) - Support more zip compression formats: bzip2, lzma, xz, zstd ([#13285](astral-sh/uv#13285)) - Add support for downloading GraalPy ([#13172](astral-sh/uv#13172)) - Improve error message when a virtual environment Python symlink is broken ([#12168](astral-sh/uv#12168)) - Use `fs_err` for paths in symlinking errors ([#13303](astral-sh/uv#13303)) - Minify and embed managed Python JSON at compile time ([#12967](astral-sh/uv#12967)) ### Preview features - Build backend: Make preview default and add configuration docs ([#12804](astral-sh/uv#12804)) - Build backend: Allow escaping in globs ([#13313](astral-sh/uv#13313)) - Build backend: Make builds reproducible across operating systems ([#13171](astral-sh/uv#13171)) ### Configuration - Add `python-downloads-json-url` option for `uv.toml` to configure custom Python installations via JSON URL ([#12974](astral-sh/uv#12974)) ### Bug fixes - Check nested IO errors for retries ([#13260](astral-sh/uv#13260)) - Accept `musllinux_1_0` as a valid platform tag ([#13289](astral-sh/uv#13289)) - Fix discovery of pre-release managed Python versions in range requests ([#13330](astral-sh/uv#13330)) - Respect locked script preferences in `uv run --with` ([#13283](astral-sh/uv#13283)) - Retry streaming downloads on broken pipe errors ([#13281](astral-sh/uv#13281)) - Treat already-installed base environment packages as preferences in `uv run --with` ([#13284](astral-sh/uv#13284)) - Avoid enumerating sources in errors for path Python requests ([#13335](astral-sh/uv#13335)) - Avoid re-creating virtual environment with `--no-sync` ([#13287](astral-sh/uv#13287)) ### Documentation - Remove outdated description of index strategy ([#13326](astral-sh/uv#13326)) - Update "Viewing the version" docs ([#13241](astral-sh/uv#13241))

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [ghcr.io/astral-sh/uv](https://github.com/astral-sh/uv) | final | patch | `0.7.2` -> `0.7.3` | --- ### Release Notes <details> <summary>astral-sh/uv (ghcr.io/astral-sh/uv)</summary> ### [`v0.7.3`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#073) [Compare Source](astral-sh/uv@0.7.2...0.7.3) ##### Enhancements - Add `--dry-run` support to `uv self update` ([#9829](astral-sh/uv#9829)) - Add `--show-with` to `uv tool list` to list packages included by `--with` ([#13264](astral-sh/uv#13264)) - De-duplicate fetched index URLs ([#13205](astral-sh/uv#13205)) - Support more zip compression formats: bzip2, lzma, xz, zstd ([#13285](astral-sh/uv#13285)) - Add support for downloading GraalPy ([#13172](astral-sh/uv#13172)) - Improve error message when a virtual environment Python symlink is broken ([#12168](astral-sh/uv#12168)) - Use `fs_err` for paths in symlinking errors ([#13303](astral-sh/uv#13303)) - Minify and embed managed Python JSON at compile time ([#12967](astral-sh/uv#12967)) ##### Preview features - Build backend: Make preview default and add configuration docs ([#12804](astral-sh/uv#12804)) - Build backend: Allow escaping in globs ([#13313](astral-sh/uv#13313)) - Build backend: Make builds reproducible across operating systems ([#13171](astral-sh/uv#13171)) ##### Configuration - Add `python-downloads-json-url` option for `uv.toml` to configure custom Python installations via JSON URL ([#12974](astral-sh/uv#12974)) ##### Bug fixes - Check nested IO errors for retries ([#13260](astral-sh/uv#13260)) - Accept `musllinux_1_0` as a valid platform tag ([#13289](astral-sh/uv#13289)) - Fix discovery of pre-release managed Python versions in range requests ([#13330](astral-sh/uv#13330)) - Respect locked script preferences in `uv run --with` ([#13283](astral-sh/uv#13283)) - Retry streaming downloads on broken pipe errors ([#13281](astral-sh/uv#13281)) - Treat already-installed base environment packages as preferences in `uv run --with` ([#13284](astral-sh/uv#13284)) - Avoid enumerating sources in errors for path Python requests ([#13335](astral-sh/uv#13335)) - Avoid re-creating virtual environment with `--no-sync` ([#13287](astral-sh/uv#13287)) ##### Documentatio...

konstin added the error messages Messaging when something goes wrong label Mar 14, 2025

konstin requested review from jtfmumm and zanieb March 14, 2025 14:02

zanieb reviewed Apr 16, 2025

View reviewed changes

zanieb changed the title ~~Hint for broken venv~~ Improve error message when a virtual environment Python symlink is broken Apr 16, 2025

zanieb reviewed Apr 16, 2025

View reviewed changes

konstin force-pushed the konsti/hint-about-broken-venv branch from b3139bf to 32674b4 Compare April 16, 2025 22:25

konstin added 5 commits May 7, 2025 18:57

Style

2c633b2

Handle downstream variant matching

a0b008b

Add test

9b2ce8e

Review: Check if we're in a venv

51823d4

konstin force-pushed the konsti/hint-about-broken-venv branch from 32674b4 to 51823d4 Compare May 7, 2025 17:14

zanieb reviewed May 7, 2025

View reviewed changes

Review: Handle the non-venv branch, too

240feb5

zanieb approved these changes May 7, 2025

View reviewed changes

Test system interpreter behavior

525a200

zanieb reviewed May 7, 2025

View reviewed changes

zanieb mentioned this pull request May 7, 2025

Avoid enumerating sources in errors for path Python requests #13335

Merged

zanieb merged commit 364e399 into main May 7, 2025
86 checks passed

zanieb deleted the konsti/hint-about-broken-venv branch May 7, 2025 18:24

BrewTestBot mentioned this pull request May 7, 2025

uv 0.7.3 Homebrew/homebrew-core#222775

Merged

	// If the interpreter is from an active, valid virtual environment, we should
	// fail because it's broken
	if let Some(Ok(true)) = matches!(source, PythonSource::ActiveEnvironment)
	.then(\|\| {
	path.parent()
	.and_then(Path::parent)
	.map(\|path\| path.join("pyvenv.cfg").try_exists())
	})
	.flatten()
	{

	Err(InterpreterError::NotFound(_)) => Ok(Err(PythonNotFound {
	request: request.clone(),
	python_preference: preference,
	environment_preference: environments,
	})),
	Err(err) => Err(Error::Query(
	Box::new(err),
	path.clone(),
	PythonSource::ProvidedPath,
	)),

Improve error message when a virtual environment Python symlink is broken #12168

Improve error message when a virtual environment Python symlink is broken #12168

Uh oh!

Conversation

konstin commented Mar 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

charliermarsh commented Mar 14, 2025

Uh oh!

konstin commented Mar 14, 2025

Uh oh!

zanieb commented Apr 16, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

konstin commented Apr 16, 2025

Uh oh!

zanieb commented Apr 16, 2025

Uh oh!

konstin commented Apr 16, 2025

Uh oh!

konstin commented May 6, 2025

Uh oh!

zanieb commented May 6, 2025

Uh oh!

konstin commented May 6, 2025

Uh oh!

zanieb May 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

zanieb commented May 7, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

konstin commented Mar 14, 2025 •

edited

Loading

zanieb May 7, 2025 •

edited

Loading