Repository navigation
Version limitations for optional dependencies are ignored #12121
Description
This may be just the expected side effect of how packaging/pip works. Nevertheless, it may be something worth at least documenting as users may run into surprises, too.
PR #11934 dropped the support for mpl 3.0.x, yet the tests for using version 3.0.3 happily run rather than raising an error or try to update.
Activity
saimn commentedon Sep 3, 2021
I tried locally on another repo and it works. So probably another cache issue with CircleCI. Actually it shouldn't have run
image-tests-mpl303since you deleted this job in the PR ?bsipocz commentedon Sep 3, 2021
I've deleted that job in a later commit.
neutrinoceros commentedon Jan 21, 2026
oldestdepsjobs recently received consolidations that I think make this issue moot (at least for the CI part). I suggest closing this.bsipocz commentedon Jan 21, 2026
FWIW, this was never a CI issue.
pllim commentedon Jan 21, 2026
Even so, if users now install oldest deps as we do in CI, they shouldn't accidentally be using too old a version. If people do pip install a la cart, then pip now complains if it finds conflict in resolving the pins, and it is also not our problem. So, what remains to be addressed here?
bsipocz commentedon Jan 21, 2026
yeap, it's upstream. I believe pip still won't complain for optional dependency version limits, those are just ignored -- and that was the original problem. No need to reopen, but it needed to be clarified this wasn't a CI issue and is very likely is still an issue.
pllim commentedon Jan 21, 2026
Do you have a suggestion where to add this to doc?