astral-sh/uv

Add environment variable to always use `--active` flag

Open

#11,273 opened on Feb 6, 2025

View on GitHub
 (15 comments) (24 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
configurationenhancementgood first issue

Description

Summary

The new --active flag (#11189) is a great addition and I think it goes some way to allow uv and pyenv to work better together (see #6204).

Would it be possible to add a new environment variable to make that flag the default? For example, the PR suggested something like UV_PROJECT_ENVIRONMENT=ACTIVE but could also be UV_ACTIVE=1. Or maybe this already works? If so, it's not clear from the documentation.

Example

No response

Contributor guide

Tech stack
rust
Domain
clideveloper 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.
1-3 hours
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
Rust programminguv CLI usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
This issue requests adding an environment variable to override the active flag behavior. The discussion in #11189 and #6204 provide context. To implement, one would need to modify the CLI argument parsing in uv, likely in the main configuration module. The maintainers have discussed possible names like UV PROJECT ENVIRONMENT=ACTIVE. The implementation should check the environment variable at startup and set the flag accordingly. See comments in the issue for additional constraints.