python-pipdeptree
Port variant py310
Summary Utility to show package dependency tree (3.10)
Package version 2.13.0
Homepage https://github.com/tox-dev/pipdeptree
Keywords python
Maintainer Python Automaton
License Not yet specified
Other variants v11
Ravenports Buildsheet | History
Ravensource Port Directory | History
Last modified 15 AUG 2023, 17:14:27 UTC
Port created 03 JAN 2023, 14:55:16 UTC
Subpackage Descriptions
single # pipdeptree [PyPI] [Supported Python versions] [Downloads] [check] [![pre-commit.ci status]](https://results.pre-commit.ci/latest/github/tox-dev/pipdeptree/main) `pipdeptree` is a command line utility for displaying the installed python packages in form of a dependency tree. It works for packages installed globally on a machine as well as in a virtualenv. Since `pip freeze` shows all dependencies as a flat list, finding out which are the top level packages and which packages do they depend on requires some effort. It\'s also tedious to resolve conflicting dependencies that could have been installed because older version of `pip` didn\'t have true dependency resolution[^1]. `pipdeptree` can help here by identifying conflicting dependencies installed in the environment. To some extent, `pipdeptree` is inspired by the `lein deps :tree` command of [Leiningen]. ## Installation `bash pip install pipdeptree ` ## Running in virtualenvs `New in ver. 2.0.0` If you want to run pipdeptree in the context of a particular virtualenv, you can specify the `--python` option. Note that this capability has been recently added in version `2.0.0`. Alternatively, you may also install pipdeptree inside the virtualenv and then run it from there. ## Usage and examples To give you a brief idea, here is the output of `pipdeptree` compared with `pip freeze`: ```bash $ pip freeze Flask==0.10.1 itsdangerous==0.24 Jinja2==2.11.2 -e git+git@github.com:naiquevin/lookupy.git@cdbe30c160e1c29802df75e145ea4ad903c05386#egg=Lookupy MarkupSafe==0.22 pipdeptree @ file:///private/tmp/pipdeptree-2.0.0b1-py3-none-any.whl Werkzeug==0.11.2 ``` And now see what `pipdeptree` outputs, ```bash $ pipdeptree Warning!!! Possibly conflicting dependencies found: * Jinja2==2.11.2 - MarkupSafe [required: >=0.23, installed: 0.22] ------------------------------------------------------------------------ Flask==0.10.1 - itsdangerous [required: >=0.21, installed: 0.24] - Jinja2 [required: >=2.4, installed: 2.11.2] - MarkupSafe [required: >=0.23, installed: 0.22] - Werkzeug [required: >=0.7, installed: 0.11.2] Lookupy==0.1 pipdeptree==2.0.0b1 - pip [required: >=6.0.0, installed: 20.1.1] setuptools==47.1.1 wheel==0.34.2 ``` ## Is it possible to find out why a particular package is installed? `New in ver. 0.5.0` Yes, there\'s a `--reverse` (or simply `-r`) flag for this. To find out which packages depend on a particular package(s), it can be combined with `--packages` option as follows: ```bash $ pipdeptree --reverse --packages itsdangerous,MarkupSafe Warning!!! Possibly conflicting dependencies found: * Jinja2==2.11.2 - MarkupSafe [required: >=0.23, installed: 0.22] ------------------------------------------------------------------------ itsdangerous==0.24 - Flask==0.10.1 [requires: itsdangerous>=0.21] MarkupSafe==0.22 - Jinja2==2.11.2 [requires: MarkupSafe>=0.23] - Flask==0.10.1 [requires: Jinja2>=2.4] ```
Configuration Switches (platform-specific settings discarded)
PY310 ON Build using Python 3.10 PY311 OFF Build using Python 3.11
Package Dependencies by Type
Build (only) python-pip:single:py310
autoselect-python:single:standard
Build and Runtime python310:single:standard
Download groups
main mirror://PYPIWHL/1a/16/dcf8dab5bde96006502d80c858676728364e307f23c3df210fc1f6f406ee
Distribution File Information
70c582224a41f20c4b69be7aaeeed40b59d3f247a93b4d6891b3d772c9befc94 26552 pipdeptree-2.13.0-py3-none-any.whl
Ports that require python-pipdeptree:py310
No other ports depend on this one.