astral-sh/uv

Allow `uv add` sources to be specified outside of the requirement

Open

#5,381 opened on Jul 23, 2024

View on GitHub
 (1 comment) (4 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
clihelp wantedtracking

Description

e.g.

uv add [<package>] --git <url> 
uv add [<package>] --path <path> 
uv add [<package>] --url <url> 
uv add [<package>] --workspace <path>

These user should be able to optionally include the package name and specifiers, e.g. uv add "httpx>0.2.0" --git https://github.com/encode/httpx

See:

  • #5383
  • #5384
  • #5385
  • #5386

Contributor guide

Tech stack
rustpython
Domain
clitooling
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-2 days
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
Rust basicsCLI argument parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Review the existing argparse module in src/cli/ to understand how current `uv add` handles package specs. Investigate how other commands like `uv pip install` handle source flags. Check the referenced issues #5383-5386 for design discussions. The main implementation would involve modifying the `add` subcommand to accept optional source flags and integrate them with the requirement string parsing.