Charlie Marsh 22fd9f7ff1 Pass extra when evaluating lockfile markers (#9539) ... ## Summary When we serialize and deserialize the lockfile, we remove the conflict markers. So in the linked case, the edges for the `tqdm` entries are like: ``` complexified_marker: UniversalMarker { pep508_marker: python_full_version >= '3.9.0', conflict_marker: true, }, ``` However... when we evaluate in-memory, the conflict markers are still there... ``` complexified_marker: UniversalMarker { pep508_marker: true, conflict_marker: extra == 't1' and extra != 't2', }, ``` So if `uv run` creates the lockfile, we evaluate this as `false`. We should make this consistent, and I expect @BurntSushi is aware. But for now, it's reasonable / correct to pass the extra when evaluating at this specific point, since we know the dependency was enabled by the marker. Closes https://github.com/astral-sh/uv/issues/9533#issuecomment-2508908591.		2024-11-30 14:22:18 +00:00
..
src	Pass extra when evaluating lockfile markers (#9539)	2024-11-30 14:22:18 +00:00
Cargo.toml	uv-pypi-types: make room for group names in addition to extras	2024-11-14 08:02:46 -05:00