astral-sh/uv

Hint supported interpreter request formats on missing toolchain

Open

#4,401 opened on Jun 18, 2024

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

Description

We should hint the supported formats when we can't find a toolchain and the request is parsed as an executable name (which is our final fallback).

Contributor guide

Tech stack
rust
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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 knowledgefamiliarity with uv toolchain resolution
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate how uv parses interpreter requests and falls back to executable names. Locate the relevant code in the toolchain resolution module, likely in a file handling toolchain lookup. Add logic to detect when a request is parsed as an executable name and produce a hint listing supported formats (e.g., `<name>@<version>`, `<name>@latest`). Ensure hints are user friendly and localized.
Hint supported interpreter request formats on missing toolchain · astral-sh/uv#4401 | Good First Issue