Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Better error message if a pre dependency is not found

See original GitHub issue

I use pipenv --two and pipenv install angr aborts with:

Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches capstone>=3.0.5.rc2
Tried: 2.0, 2.1, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5rc2, 3.0.5rc2, 3.0.5rc2, 3.0.5rc2, 3.0.5rc2

Issue Analytics

State:
Created 5 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

bitwavecommented, Apr 18, 2018

Maybe some kind of this with a hint:

Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches capstone>=3.0.5.rc2
Tried: 2.0, 2.1, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5rc2, 3.0.5rc2, 3.0.5rc2, 3.0.5rc2, 3.0.5rc2

Hint: try pipenv lock --pre if it is a pre-release dependency

1reaction

uranusjrcommented, Apr 18, 2018

I agree the message can be improved. Can you modify the title to make the scope clear?