astral-sh/uv

Support `UV_ONLY_BINARY` and `UV_NO_BINARY` environment variables

Open

#4,291 opened on Jun 12, 2024

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

Description

This is useful with cibuildwheel or some other complicated tools in the CI environment.

pip has similiar PIP_NO_BINARY and PIP_ONLY_BINARY: https://pip.pypa.io/en/latest/cli/pip_install/#cmdoption-no-binary

Contributor guide

Tech stack
rustpythonshell
Domain
toolingdeveloper experience
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with RustUnderstanding of pip's no binary / only binary flags
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine how uv currently handles binary vs source distributions and environment variables. Look at the CLI argument parsing in crate `uv` or `uv installer` for existing similar flags like ` no build isolation`. Implement reading `UV NO BINARY` and `UV ONLY BINARY` environment variables, mapping them to the existing internal logic for ` no binary` and ` only binary` flags. Ensure parsing follows pip's semantics (package names or `:all:`). Consider updating docs and adding tests.