mirror of https://github.com/astral-sh/uv
a7850d2a1c
## 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. |
||
|---|---|---|
| .. | ||
| discovery.rs | ||
| downloads.inc | ||
| downloads.inc.mustache | ||
| downloads.rs | ||
| environment.rs | ||
| implementation.rs | ||
| installation.rs | ||
| interpreter.rs | ||
| lib.rs | ||
| managed.rs | ||
| platform.rs | ||
| pointer_size.rs | ||
| prefix.rs | ||
| py_launcher.rs | ||
| python_version.rs | ||
| target.rs | ||
| version_files.rs | ||
| virtualenv.rs | ||
| which.rs | ||