Charlie Marsh 71df509d09 Avoid adding non-extra package with extra dependencies (#9540) ... ## Summary Previously, when we encountered `foo[bar]`, we'd add a dependency on `PubGrubPackage::Package` for `foo`, and then `PubGrubPackage::Extra` for `foo[bar]`. Later, when we ask for the dependencies of the `PubGrubPackage::Extra`, we add `PubGrubPackage::Package` for `foo`, and `PubGrubPackage::Package` for `foo[bar]`. This is an intentional strategy because it ensures that PubGrub "knows" that these have to be solved to the same version as early as possible. It turns out that the first part here ("add a dependency on `PubGrubPackage::Package` for `foo`") is suboptimal, because it means PubGrub might try to solve _just_ `foo` without realizing that it also has to accommodate all the constraints from the extra. Instead, we now add _just_ `PubGrubPackage::Extra` for `foo[bar]`, and defer adding the base package. It looks like this leads to a far more efficient solve for Airflow.		2024-12-01 08:42:27 -05:00
..
src	Avoid adding non-extra package with extra dependencies (#9540)	2024-12-01 08:42:27 -05:00
Cargo.toml	uv-pypi-types: make room for group names in addition to extras	2024-11-14 08:02:46 -05:00