9efbc1fc25
## Summary This PR adds the `--prompt` option to `venv` subcommand. The default behavior for `uv venv` is to create a virtual environment in the current directory with `.venv` name. This is different from `venv` / `virtualenv` where a user always needs to provide the virtual environment path. This allows us to define our own behavior in the default scenario (`uv venv`). We've decided to use the current directory's name in that case. Workflows: | Command | Virtual Environment Name | Prompt | |--------|--------|--------| | `uv venv` | `.venv` (default) | Current directory name | | `uv venv project` | `project` | `project` | | `uv venv --prompt .` | `.venv` | Current directory name | | `uv venv --prompt foobar` | `.venv` | `foobar` | | `uv venv project --prompt foobar` | `project` | `foobar` | Fixes #1445 ## Test Plan This is my first Rust code and I don't know how to write tests yet. I just checked the behavior manually: ``` $ cargo build $ mkdir t $ cd t $ ../target/debug/uv venv -p 3.11 $ rg -w t .venv/bin/acti* .venv/bin/activate.csh 13:setenv VIRTUAL_ENV '/Users/inada-n/work/uv/t/.venv' 20:if ('t' != "") then 21: setenv VIRTUAL_ENV_PROMPT 't' 23: setenv VIRTUAL_ENV_PROMPT "$VIRTUAL_ENV:t:q" 38: # in which case, $prompt is undefined and we wouldn't .venv/bin/activate 48:VIRTUAL_ENV='/Users/inada-n/work/uv/t/.venv' 59: VIRTUAL_ENV_PROMPT="t" .venv/bin/activate.fish 61:set -gx VIRTUAL_ENV '/Users/inada-n/work/uv/t/.venv' 73:if test -n 't' 74: set -gx VIRTUAL_ENV_PROMPT 't' .venv/bin/activate.ps1 40:if ("t" -ne "") { 41: $env:VIRTUAL_ENV_PROMPT = "t" .venv/bin/activate.nu 6:# but then simply `deactivate` won't work because it is just an alias to hide 35: let virtual_env = '/Users/inada-n/work/uv/t/.venv' 50: let virtual_env_prompt = (if ('t' | is-empty) { 53: 't' ``` --------- Co-authored-by: Dhruv Manilawala <dhruvmanila@gmail.com> |
||
|---|---|---|
| .. | ||
| bench | ||
| cache-key | ||
| distribution-filename | ||
| distribution-types | ||
| gourgeist | ||
| install-wheel-rs | ||
| once-map | ||
| pep440-rs | ||
| pep508-rs | ||
| platform-host | ||
| platform-tags | ||
| pypi-types | ||
| requirements-txt | ||
| uv | ||
| uv-build | ||
| uv-cache | ||
| uv-client | ||
| uv-dev | ||
| uv-dispatch | ||
| uv-distribution | ||
| uv-extract | ||
| uv-fs | ||
| uv-git | ||
| uv-installer | ||
| uv-interpreter | ||
| uv-normalize | ||
| uv-resolver | ||
| uv-traits | ||
| uv-trampoline | ||
| uv-warnings | ||
| README.md | ||
README.md
Crates
bench
Functionality for benchmarking uv.
cache-key
Generic functionality for caching paths, URLs, and other resources across platforms.
distribution-filename
Parse built distribution (wheel) and source distribution (sdist) filenames to extract structured metadata.
distribution-types
Abstractions for representing built distributions (wheels) and source distributions (sdists), and the sources from which they can be downloaded.
gourgeist
A venv replacement to create virtual environments in Rust.
install-wheel-rs
Install built distributions (wheels) into a virtual environment.]
once-map
A waitmap-like concurrent hash map for executing tasks
exactly once.
pep440-rs
Utilities for interacting with Python version numbers and specifiers.
pep508-rs
Utilities for interacting with PEP 508 dependency specifiers.
platform-host
Functionality for detecting the current platform (operating system, architecture, etc.).
platform-tags
Functionality for parsing and inferring Python platform tags as per PEP 425.
uv
Command-line interface for the uv package manager.
uv-build
A PEP 517-compatible build frontend for uv.
uv-cache
Functionality for caching Python packages and associated metadata.
uv-client
Client for interacting with PyPI-compatible HTTP APIs.
uv-dev
Development utilities for uv.
uv-dispatch
A centralized struct for resolving and building source distributions in isolated environments.
Implements the traits defined in uv-traits.
uv-distribution
Client for interacting with built distributions (wheels) and source distributions (sdists). Capable of fetching metadata, distribution contents, etc.
uv-extract
Utilities for extracting files from archives.
uv-fs
Utilities for interacting with the filesystem.
uv-git
Functionality for interacting with Git repositories.
uv-installer
Functionality for installing Python packages into a virtual environment.
uv-interpreter
Functionality for detecting and leveraging the current Python interpreter.
uv-normalize
Normalize package and extra names as per Python specifications.
uv-package
Types and functionality for working with Python packages, e.g., parsing wheel files.
uv-resolver
Functionality for resolving Python packages and their dependencies.
uv-traits
Shared traits for uv, to avoid circular dependencies.
pypi-types
General-purpose type definitions for types used in PyPI-compatible APIs.
uv-warnings
User-facing warnings for uv.
requirements-txt
Functionality for parsing requirements.txt files.