Damian Shaw

> We could have `VIRTUAL_ENV` take precedence over `CONDA_PREFIX` if the `python` in PATH is from that venv; I'm not sure what behavior conda users would expect. When conda is...

I can reproduce both steps on Pip 23.2.1 Python 3.9 on Linux. The resolution impossible gives the error: ``` ERROR: Cannot install -r requirements.txt (line 3) and pystac because these...

I tested this on Pip directly by creating a copy the States ahead of time and if backjumping fails falling back to the old backtracking by restoring the state and...

I created this much more tighly bounded set of requirements that fails when it shouldn't, it should be relatively resistent to any changes on PyPi and hopefully easier to debug...

An even tighter set of requirements, this resolves: ``` pandas==1.3.5 pystac==1.8.3 pystac-client==0.3.3 sat-stac==0.1.1 ``` This does not: ``` pandas>=1.3.5,=1.8.2,=0.3.2,

So, this issue appears to be that backjumping as implemented by https://github.com/sarugaku/resolvelib/pull/113 is incorrectly discarding state. I beleive this also causes Pip 23.3 to fail to install `kedro[test]==0.18.13`, I have...

Experimenting tonight with the examples a bit I beleive the assumptions in https://github.com/sarugaku/resolvelib/pull/113 that you can safely discard state until there are no intersection between the causes and the now...

Another triggering requirement, at least in Pip 23.2.1: `"aicsimageio==4.9.1" "napari-aicsimageio==0.7.2" "napari"` It no longer occurs in Pip 23.3 but that is because of optimizations applied on Pip side that seems...

> @notatallshaw 's solution seems a viable way to fix it, can you make a PR please? I don't think it is actually, it only works in the case that...

> The requirements I hit this bug with were `"boto3>=1.28.64,=0.21.5"` . Can you please provide more context on your set-up, I was able to reproduce the `ResolutionImpossible` on Python 3.10...