mirror of https://github.com/astral-sh/uv
4026710189
e.g. for scenarios that test resolution _without_ installation.
This refactors the `update` script to generate scenario test files for
`pip compile` _and_ `pip install`. We don't overlap scenarios to save
time. We only generate `pip compile` test cases for scenarios we cannot
represent with `pip install` e.g. a `--python-version` override.
The _one_ scenario I added happened to reveal a bug in our resolver
where we were incorrectly filtering versions by the installed version
when wheels were available. Per the comment at
https://github.com/astral-sh/puffin/issues/883#issuecomment-1890773112,
we should _only_ need to check for a compatible installed Python version
when using a different _target_ Python version if we need to build a
source distribution.
|
||
|---|---|---|
| .. | ||
| bench | ||
| benchmarks | ||
| compare_with_pip | ||
| editable-installs | ||
| popular_packages | ||
| requirements | ||
| scenarios | ||
| wheels | ||