"Incompatible versions in the resolved dependencies" message does not contain information on which Pipfile dependency specs are responsible for the clash. #3693
Labels
help wanted
Priority: Low
This item is low priority and may not be looked at in the next few release cycles.
Type: Enhancement 💡
This is a feature or enhancement request.
Issue description
Describe the issue briefly here.
If there are version conflicts in specified Pipfile, pipenv does not tell which lines are in conflict.
Expected result
Pipenv tells me which lines are in conflict so that I can resolve the problem.
Actual result
The pipenv graph method kind of works (??). It omits django as a root level entry which I guess signals where the problem is (?). It seems to me that this could become harder with larger Pipfiles and multiple version spec clashes.
Steps to replicate
Please run
$ pipenv --support
, and paste the results here. Don't put backticks (`
) around it! The output already contains Markdown formatting.No, It contains too much sensitive/identifiable private/client information.
pipenv, version 2018.11.26
The text was updated successfully, but these errors were encountered: