Damian Shaw

> > > > `apache-airflow[all]==1.10.13` > > This failing doesn't make sense -- there is a solution for this in the space that the resolver is exploring? > > Doesn't...

> > > Yes, apache-airflow 1.10.13 can not actually pass the new resolver due to internal conflicts. From my understanding they spent a ton of time cleaning this up to...

Actually @pradyunsg is correct, `airflow[all]==1.10.13` does have a solution. My latest experimental version of using back jumps is able to find a solution to this requirement pretty quickly. I think...

> That might be what #91 is about as well. Yes, going to be watching that issue, if a PR is developed I will test it against this use case....

> Remember that `pip check` does not take extras into account so `pip check` passing isn't that meaningful for this particular case (IIRC the base Airflow resolves very quickly even...

I've not had a lot of time to work on this and since pip 21.3 was released no one has reported any very significant backtracking times to the pip tracker...

I'm not familiar with this repo but FYI this particular example `pyrax==1.9.8` seems to have been fixed in pip by https://github.com/pypa/pip/issues/10479

I know this kind of request has been brought up before and is a little problematic because Pip doesn't consider what is installed in the existing environment on a new...

> Facing same issue :-( Exactly the same as listed above with the same requirements? Or do you have different requirements and therefore could provide different steps to reproduce? I...

> The original error only happened when the full set of requirements was specified. > Therefore, the issue does not seem to be related to missing wheels. > A clearer...