astral-sh/uv

Improve display of executable install errors during `uv python install`

Open

#9,707 opened on Dec 7, 2024

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
error messageshelp wanted

Description

e.g.,

error: Failed to install cpython-3.13.0-macos-aarch64-none
  Caused by: Executable already exists at `/Users/zb/.local/bin/python3` but is not managed by uv; use `--force` to replace it
error: Failed to install cpython-3.13.0-macos-aarch64-none
  Caused by: Executable already exists at `/Users/zb/.local/bin/python` but is not managed by uv; use `--force` to replace it

we show ~the same message twice. It'd be nice to group these.

Contributor guide

Tech stack
rust
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Rust knowledgeUnderstanding of uv's error handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue describes duplicate error messages during `uv python install`. Investigate the error handling in the installer code, likely in the `crates/` directory. Look for where executable install errors are generated and displayed. The goal is to group similar errors (e.g., same cause for different executables) so they appear once. Check how other errors are formatted in the codebase for consistency.
Improve display of executable install errors during `uv python install` · astral-sh/uv#9707 | Good First Issue