![]() This commit adds marker expressions to our `Fork` type, which are in turn passed down into `PubGrubDependencies::from_requirements` to filter our any dependencies with markers that are disjoint from the fork's marker expression. This is necessary to avoid visiting packages in the dependency graph that can never actually be installed. This is because when a fork is created in the resolver, it always happens when there are two sibling dependency specifications on a package with the same name, but with non-overlapping marker expressions. Each fork corresponds to each such conflicting dependency specification, and each fork assumes the the corresponding marker expression as a pre-condition for any future dependencies considered by it. That is, since the fork represents an installation path that can only be taken when the corresponding dependency specification (and its marker expression) is actually used, it also therefore follows that the marker expression is true. Therefore, any dependency visited in that fork with a marker expression that cannot possibly be true when the markers of the fork are true can and ought to be completely ignored. |
||
---|---|---|
.. | ||
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-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-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.