You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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]
The text was updated successfully, but these errors were encountered:
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.
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:
And sometimes I also get seeming contradictory dependency listings (yes, I did use -r -l here too):
The text was updated successfully, but these errors were encountered: