-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version conflicts should indicate which dependencies have conflicting requirements #1687
Labels
Type: Enhancement 💡
This is a feature or enhancement request.
Comments
pull requests accepted! |
kennethreitz
added
the
Type: Enhancement 💡
This is a feature or enhancement request.
label
Mar 12, 2018
closing for #1693 |
Closed
gsemet
added a commit
to gsemet/pipenv
that referenced
this issue
Mar 13, 2018
Fix pypa#1696 Fix pypa#1687 Reference pypa#1693 Signed-off-by: Gaetan Semet <[email protected]>
gsemet
added a commit
to gsemet/pipenv
that referenced
this issue
Mar 14, 2018
Fix pypa#1696 Fix pypa#1687 Reference pypa#1693 Signed-off-by: Gaetan Semet <[email protected]>
Hi, #1693 is unrelated to this issue. This issue is about the UX of having a mismatch in the dependency tree. |
gsemet
added a commit
to gsemet/pipenv
that referenced
this issue
Mar 31, 2018
Fix pypa#1696 Fix pypa#1687 Reference pypa#1693 Signed-off-by: Gaetan Semet <[email protected]>
Can this issue be opened again? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run
pipenv install
and there's a conflict in versions, it doesn't tell me what caused those conflicting versions. This makes it unnecessarily difficult to figure out what's wrong with the dependency graph.Expected result
Actual result
The text was updated successfully, but these errors were encountered: