-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
PR #132 and additional commits on top of it #138
Conversation
This handles the case where the same package is part of 2 different extra_require profiles for eg. {'rsa': ['cryptography'], 'signals': ['blinker'], 'signedtoken': ['cryptography', 'pyjwt>=1.0.0']} The above is the extra_require dict for oauthlib. Since 'cryptography' is an extra require in multiple profiles, this caused duplicate ReqPackage objects to be present in the tree. As a result of deduplicating, no additional filtering is required in presentation logic (ie. 'render_text' and 'dump_graphviz' functions).
If a package is specified using the '-p' option and it also happens to be one of the dependencies of another package (also specified as part of '-p' option), then the top level package itself is skipped from the output. For eg. consider following call $ pipdeptree -p 'abc,tox' Now if 'tox' also happens to be the dependency of 'abc', then it's not shown in the output unless '-a' flag (show all) is also specified. This seems to be an old bug that has surfaced now with support for extra requirements. There are cases where a package can be a dependent of itself via extra requirements eg. tox depends on pluggy and pluggy[dev] also depends on tox.
108ca75
to
beacb88
Compare
A lot of code has been refactored in this commit
* master: Fix github checks due to set-env deprecation Shield newline symbol when generating labels for graphviz
Seems we'll no longer proceed with this. |
@gaborbernat This PR was for #107. IIRC, this code was mostly working but as it is an intrusive change I wanted to do a beta release first. Never got to it. It's unlikely that I'll be working on it any time soon but JFYI because the PR is closed whereas issue #107 is still open. If anyone wants to pursue the functionality, this PR can be a good starting point. |
I am sorry, I would like to help, but I no longer need this functionality and I have no time to continue working on it. |
No description provided.