Updated graph command docstrings, fixes #3071#3252
Closed
ROldford wants to merge 2 commits intopypa:masterfrom
Closed
Updated graph command docstrings, fixes #3071#3252ROldford wants to merge 2 commits intopypa:masterfrom
ROldford wants to merge 2 commits intopypa:masterfrom
Conversation
frostming
added
the
Type: Question ❔
Member
|
I'm fairly sure this isn't a desired behavior... I have no idea why this would be the case either... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The issue
#3071 - pipenv graph only shows dev dependencies instead of all dependencies
The fix
Since graph depends on pipdeptree, fixing graph's interaction with shell is not really doable, so documentation has been edited to reflect how graph works differently in and out of shell.
The checklist
news/directory to describe this fix with the extension.bugfix,.feature,.behavior,.doc..vendor. or.trivial(this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.