Charlie Marsh a7850d2a1c Use separate types to represent raw vs. resolver markers (#6646) ... ## Summary This is similar to https://github.com/astral-sh/uv/pull/6171 but more expansive... _Anywhere_ that we test requirements for platform compatibility, we _need_ to respect the resolver-friendly markers. In fixing the motivating issue (#6621), I also realized that we had a bunch of bugs here around `pip install` with `--python-platform` and `--python-version`, because we always performed our `satisfy` and `Plan` operations on the interpreter's markers, not the adjusted markers! Closes https://github.com/astral-sh/uv/issues/6621.		2024-08-26 18:00:21 +00:00
..
benches	Use separate types to represent raw vs. resolver markers (#6646)	2024-08-26 18:00:21 +00:00
inputs	distribution-filename: speed up is_compatible (#367)	2023-11-09 09:01:03 -05:00
src	Upgrade to Rust 1.80.0 (#5472)	2024-07-27 01:49:47 +00:00
Cargo.toml	switch to jiff from chrono (#6205)	2024-08-20 11:31:46 -05:00