1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
3 NAMEBASE= python-pipdeptree
7 SDESC[py310]= Utility to show package dependency tree (3.10)
8 SDESC[v11]= Utility to show package dependency tree (3.11)
9 HOMEPAGE= https://github.com/tox-dev/pipdeptree
10 CONTACT= Python_Automaton[python@ironwolf.systems]
13 SITES[main]= PYPIWHL/f6/22/a914ba0a65014e07aca43f89e03b3b10d579d9b3f1aab2d6a954df455988
14 DISTFILE[1]= pipdeptree-2.12.0-py3-none-any.whl:main
19 OPTIONS_AVAILABLE= PY310 PY311
20 OPTIONS_STANDARD= none
21 VOPTS[py310]= PY310=ON PY311=OFF
22 VOPTS[v11]= PY310=OFF PY311=ON
24 DISTNAME= pipdeptree-2.12.0.dist-info
28 [PY310].USES_ON= python:py310,wheel
30 [PY311].USES_ON= python:v11,wheel
32 [FILE:2938:descriptions/desc.single]
41 status]](https://results.pre-commit.ci/latest/github/tox-dev/pipdeptree/main)
43 `pipdeptree` is a command line utility for displaying the installed python
44 packages in form of a dependency tree. It
45 works for packages installed globally on a machine as well as in a
46 virtualenv. Since `pip freeze` shows all dependencies
47 as a flat list, finding out which are the top level packages and which
48 packages do they depend on requires some effort.
49 It\'s also tedious to resolve conflicting dependencies that could have been
50 installed because older version of `pip`
51 didn\'t have true dependency resolution[^1]. `pipdeptree` can help here by
52 identifying conflicting dependencies
53 installed in the environment.
55 To some extent, `pipdeptree` is inspired by the `lein deps :tree` command
61 pip install pipdeptree
64 ## Running in virtualenvs
68 If you want to run pipdeptree in the context of a particular virtualenv,
69 you can specify the `--python` option. Note
70 that this capability has been recently added in version `2.0.0`.
72 Alternatively, you may also install pipdeptree inside the virtualenv and
73 then run it from there.
77 To give you a brief idea, here is the output of `pipdeptree` compared with
86 git+git@github.com:naiquevin/lookupy.git@cdbe30c160e1c29802df75e145ea4ad903c05386#egg=Lookupy
88 pipdeptree @ file:///private/tmp/pipdeptree-2.0.0b1-py3-none-any.whl
92 And now see what `pipdeptree` outputs,
96 Warning!!! Possibly conflicting dependencies found:
98 - MarkupSafe [required: >=0.23, installed: 0.22]
99 ------------------------------------------------------------------------
101 - itsdangerous [required: >=0.21, installed: 0.24]
102 - Jinja2 [required: >=2.4, installed: 2.11.2]
103 - MarkupSafe [required: >=0.23, installed: 0.22]
104 - Werkzeug [required: >=0.7, installed: 0.11.2]
107 - pip [required: >=6.0.0, installed: 20.1.1]
112 ## Is it possible to find out why a particular package is installed?
116 Yes, there\'s a `--reverse` (or simply `-r`) flag for this. To find out
117 which packages depend on a particular
118 package(s), it can be combined with `--packages` option as follows:
121 $ pipdeptree --reverse --packages itsdangerous,MarkupSafe
122 Warning!!! Possibly conflicting dependencies found:
124 - MarkupSafe [required: >=0.23, installed: 0.22]
125 ------------------------------------------------------------------------
127 - Flask==0.10.1 [requires: itsdangerous>=0.21]
129 - Jinja2==2.11.2 [requires: MarkupSafe>=0.23]
130 - Flask==0.10.1 [requires: Jinja2>=2.4]
136 9b1f82b2a7b9755e0f8d97bdc461161dcfaf20844fd9b34df55d1cffa933925c 26140 pipdeptree-2.12.0-py3-none-any.whl