Andrew Gallant
7a5571fa5c
While writing tests for a new flag (`--emit-marker-expression`) for `uv pip compile`, I noticed that one of my test cases (`pendulum 3.0.0`) was published in Dec 2023. I wanted to include this package in my tests, but since it comes after our `EXCLUDE_NEWER` constant, it wasn't visible to `uv`. In this PR, I chose to resolve this by bumping `EXCLUDE_NEWER` to `2024-03-25T00:00:00Z`. I also considered a couple other options: * For a specific test, override and provide a custom `--exclude-newer` flag. I felt like this would maybe be okay, but we could easily wind up in a situation where we do this a lot and have a bunch of different `--exclude-newer` flags in our tests. I'm not sure if this is a huge problem in practice. Maybe it's fine. * Find another package (or invent one) with a similarly interesting configuration. It seemed easier to just bump `EXCLUDE_NEWER`. The way I did this was to run `cargo insta test` after bumping `EXCLUDE_NEWER`. I then reviewed the snapshot diffs, and if they looked reasonable, I accepted them. There was only one case where I changed the test to preserve what I thought it was trying to test. That's isolated in its own commit.
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-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-requirements
Utilities for reading package requirements from pyproject.toml and requirements.txt 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-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.