Skip to content
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

The reverse view should group all the packages that require a certain package together. #49

Closed
eli-b opened this issue Jul 6, 2016 · 3 comments

Comments

@eli-b
Copy link
Contributor

eli-b commented Jul 6, 2016

When using pipdeptree -l -r, it's confusing to see the same package listed multiple times in the (long) list of required packages. It can lead a user to incorrectly think a package is only required by one package, because they didn't notice the package is listed again elsewhere in the output.

Also, the same dependency is sometimes listed more than once. For example, I get:

six==1.10.0

  • protobuf==3.0.0b2.post2 [requires: six>=1.1.0]
    • gcloud==0.12.0 [requires: protobuf]
      six==1.10.0
  • protobuf==3.0.0b2.post2 [requires: six]
    • gcloud==0.12.0 [requires: protobuf]

And sometimes I also get seeming contradictory dependency listings (yes, I did use -r -l here too):

six==1.10.0

  • Paste==2.0.3 [requires: six>=1.3.0]
    • pysaml2==4.0.5 [requires: Paste]
      six==1.10.0
  • Paste==2.0.3 [requires: six>=1.5]
    • pysaml2==4.0.5 [requires: Paste]
@naiquevin
Copy link
Contributor

Duplicate of #45. I haven't had the time to look into this :-(. Will try to find some time this month. Feel free to submit pull requests.

@eli-b
Copy link
Contributor Author

eli-b commented Jul 6, 2016

My point here was mostly about the need to group requiring packages in the
same place to avoid confusion.
The curious examples I gave were an aside. I should have been clearer about
the main subject.

בתאריך יום ד׳, 6 ביולי 2016, 20:24, מאת Vineet Naik ‏<
notifications@github.com>:

Duplicate of #45 #45. I
haven't had the time to look into this :-(. Will try to find some time this
month. Feel free to submit pull requests.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#49 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAy9t8qwG8ecN0BjV-TMy7Nmu6J6n8f1ks5qS-S6gaJpZM4JGEkH
.

naiquevin added a commit that referenced this issue Aug 6, 2016
@naiquevin
Copy link
Contributor

Fix included in the 0.7.0 release on PyPI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants