This is dope

Excited!

Thanks for your contribution!

Overall, I am on board with the idea :-)

However, I think, as it is, the output is not clear enough.

For the "non-tree" display, we could output complete sentences that describe why the package is required.

For the "tree" display, we could highlight the required package in the tree for better visibility.

Here is a proof of concept:

This looks awesome, and I would love to have it!

Re: @sdispater's suggestion, I can take or leave the phrasing or the highlighting; I think the meaning of the output is already quite clear given the context. However, I'd like to note that (1) I like that it specifies the root project as a direct dependent when applicable and (2) specified version ranges are more useful than resolved versions in many cases, but showing both seems good too.

Why does tox appear twice in the example?

Hi,

@sdispater
I added the highlighting and the descriptions.

@seansfkelley
The resolved versions in the tree view seems like a good idea. However this PR is about adding --why option. And I want to touch the tree display logic as little as possible. Perhaps it can be a part of other Issue/PR.

Cheers

That makes sense; the formatting changes can be a different change. I didn't know --tree existed and I've never used it, so I didn't realize that the formatting of the version specifiers was existing behavior.

Maintainers, could this be merged and released please?

If anyone's looking for a solution, I have a couple of helpers that parse the poetry.lock for both requires and required by dependencies:

It shows the output more or less instantly

./deps pytest  0.07s user 0.02s system 196% cpu 0.045 total        
poetry show pytest  2.35s user 0.10s system 99% cpu 2.456 total

Feel free to use it! Best to chmod u+x this-file and move it to ~/.local/bin. It works with poetry 1.1.3 lock files and I've also read 1.0.10 with it I think.

_RED='\\\\e[1;31m&\\\\e[0m'
_GREEN='\\\\e[1;32m&\\\\e[0m'
_YELLOW='\\\\e[1;33m&\\\\e[0m'
_format () {
    tr -d '"' |
        sed "s/ \+>[^ ]* \+<.*/$_YELLOW/" | # ~ / ^ / < >= ~ a window
        sed "s/ \+>[^ ]* *$/$_GREEN/" |     # >= no upper limit
        sed "/>/ !s/<.*$/$_RED/" |          # < ~ upper limit
        sed "/>\|</ !s/ .*/  $_RED/"        # == ~ locked version
}

_requires () {
    sed -n "/^name = \"$1\"/I,/\[\[package\]\]/{
                /\[package.dep/,/^$/{
                    /^[^[]/ {
                        s/= {version = \(\"[^\"]*\"\).*/, \1/p;
                        s/ =/,/gp
             }}}" poetry.lock |
        sed "/,.*,/!s/</,</; s/^[^<]\+$/&,/" |
        column -t -s , | _format
}

_required_by () {
    sed -n "/\[metadata\]/,//d;
            /\[package\]\|\[package\.depen/,/^$/H;
            /^name\|^$1 = /Ip" poetry.lock |
        sed -n "/^$1/I{x;G;p};h" |
        sed 's/.*"\(.*\)".*/\1/' |
        sed '$!N;s/\n/ /' |
        column -t | _format
}

deps() {
    echo
    echo -e "\e[1mREQUIRES\e[0m"
    _requires "$1" | xargs -i echo -e "\t{}"
    echo
    echo -e "\e[1mREQUIRED BY\e[0m"
    _required_by "$1" | xargs -i echo -e "\t{}"
    echo
}

deps $1

--why option is already present in master branch. Closing.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.