History

Charlie Marsh 3188d99f39 Use consistent commas around i.e. and e.g. (#12157 ) ## Summary Only in user-facing docs -- I didn't bother with the rustdoc. (This is in the style guide already.)		2025-03-13 23:42:10 +00:00
..
src	Edition 2024 prep: Escape `r#gen` and remove redundant ref (#11922 )	2025-03-03 11:13:56 +00:00
Cargo.toml	Use `ArcStr` for marker values (#10453 )	2025-01-10 15:15:12 -05:00
Changelog.md	Add `uv-` prefix to all internal crates (#7853 )	2024-10-01 20:15:32 -04:00
License-Apache	Add `uv-` prefix to all internal crates (#7853 )	2024-10-01 20:15:32 -04:00
License-BSD	Add `uv-` prefix to all internal crates (#7853 )	2024-10-01 20:15:32 -04:00
Readme.md	Use consistent commas around i.e. and e.g. (#12157 )	2025-03-13 23:42:10 +00:00

Readme.md

Dependency specifiers (PEP 508) in Rust

A library for dependency specifiers, previously known as PEP 508.

Usage

use std::str::FromStr;
use pep508_rs::Requirement;

let marker = r#"requests [security,tests] >= 2.8.1, == 2.8.* ; python_version > "3.8""#;
let dependency_specification = Requirement::from_str(marker).unwrap();
assert_eq!(dependency_specification.name, "requests");
assert_eq!(dependency_specification.extras, Some(vec!["security".to_string(), "tests".to_string()]));

Markers

Markers allow you to install dependencies only in specific environments (python version, operating system, architecture, etc.) or when a specific feature is activated. E.g., you can say importlib-metadata ; python_version < "3.8" or itsdangerous (>=1.1.0) ; extra == 'security'. Unfortunately, the marker grammar has some oversights (e.g. https://github.com/pypa/packaging.python.org/pull/1181) and the design of comparisons (PEP 440 comparisons with lexicographic fallback) leads to confusing outcomes. This implementation tries to carefully validate everything and emit warnings whenever bogus comparisons with unintended semantics are made.