![]() The journey here can be seen in: - #4587 - #4589 - #4594 I collapsed all the commits here because only the last one in the stack got us to a "correct" error message. There are a few architectural changes: - We have a dedicated `MissingEnvironment` and `EnvironmentNotFound` type for `PythonEnvironment::find` allowing different error messages when searching for environments - `ToolchainNotFound` becomes a struct with the `ToolchainRequest` which greatly simplifies missing toolchain error formatting - `ToolchainNotFound` tracks the `EnvironmentPreference` so it can accurately report the locations checked The messages look like this now, instead of the bland (and often incorrect): "No Python interpreter found in system toolchains". ``` ❯ cargo run -q -- pip sync requirements.txt error: No virtual environment found ❯ UV_TEST_PYTHON_PATH="" cargo run -q -- pip sync requirements.txt --system error: No system environment found ❯ UV_TEST_PYTHON_PATH="" cargo run -q -- pip sync requirements.txt --python 3.12 error: No virtual environment found for Python 3.12 ❯ UV_TEST_PYTHON_PATH="" cargo run -q -- pip sync requirements.txt --python 3.12 --system error: No system environment found for Python 3.12 ❯ UV_TEST_PYTHON_PATH="" cargo run -q -- toolchain find 3.12 --preview error: No toolchain found for Python 3.12 in system path ❯ UV_TEST_PYTHON_PATH="" cargo run -q -- pip compile requirements.in error: No toolchain found in virtual environments or system path ``` I'd like to follow this with hints, suggesting creating an environment or using system in some cases. |
||
---|---|---|
.. | ||
bench | ||
cache-key | ||
distribution-filename | ||
distribution-types | ||
install-wheel-rs | ||
once-map | ||
pep440-rs | ||
pep508-rs | ||
platform-tags | ||
pypi-types | ||
requirements-txt | ||
uv | ||
uv-auth | ||
uv-build | ||
uv-cache | ||
uv-cli | ||
uv-client | ||
uv-configuration | ||
uv-dev | ||
uv-dispatch | ||
uv-distribution | ||
uv-extract | ||
uv-fs | ||
uv-git | ||
uv-installer | ||
uv-macros | ||
uv-normalize | ||
uv-requirements | ||
uv-resolver | ||
uv-settings | ||
uv-state | ||
uv-tool | ||
uv-toolchain | ||
uv-trampoline | ||
uv-types | ||
uv-version | ||
uv-virtualenv | ||
uv-warnings | ||
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.
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-types
.
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-toolchain
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-requirements
Utilities for reading package requirements from pyproject.toml
and requirements.txt
files.
uv-resolver
Functionality for resolving Python packages and their dependencies.
uv-types
Shared traits for uv, to avoid circular dependencies.
pypi-types
General-purpose type definitions for types used in PyPI-compatible APIs.
uv-virtualenv
A venv
replacement to create virtual environments in Rust.
uv-warnings
User-facing warnings for uv.
requirements-txt
Functionality for parsing requirements.txt
files.