there’s a known resolver caching bug where a prior resolve for

python-dateutil>=2.1,<3.0.0

could pin to the highest available version - and then if you were to subsequently add

python-dateutil==2.5.3

into the mix it would be unsatisfiable because the range’d resolve would be cached at that higher version. the arg I mentioned should help if that’s the case.