konsti 750e8b1e2f Remove propagate_markers (#7076) ... Follow-up to #6959 and #6961: Use the reachability computation instead of `propagate_markers` everywhere. With `marker_reachability`, we have a function that computes for each node the markers under which it is (`requirements.txt`, no markers provided on installation) or can be (`uv.lock`, depending on the markers provided on installation) included in the installation. Put differently: If the marker computed by `marker_reachability` is not fulfilled for the current platform, the package is never required on the current platform. We compute the markers for each package in the graph, this includes the virtual extra packages and the base packages. Since we know that each virtual extra package depends on its base package (`foo[bar]` implied `foo`), we only retain the base package marker in the `requirements.txt` graph. In #6959/#6961 we were only using it for pruning packages in `uv.lock`, now we're also using it for the markers in `requirements.txt`. I think this closes #4645, CC @bluss.		2024-09-05 16:52:21 +00:00
..
src	Remove propagate_markers (#7076)	2024-09-05 16:52:21 +00:00
Cargo.toml	switch to jiff from chrono (#6205)	2024-08-20 11:31:46 -05:00