https://github.com/tilboerner/depx
Examine and visualize dependencies used by Python modules 🔍
https://github.com/tilboerner/depx
dependencies graph networkx python
Last synced: 3 months ago
JSON representation
Examine and visualize dependencies used by Python modules 🔍
- Host: GitHub
- URL: https://github.com/tilboerner/depx
- Owner: tilboerner
- License: other
- Created: 2019-03-15T10:21:47.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2022-12-08T07:42:48.000Z (about 3 years ago)
- Last Synced: 2025-03-27T12:11:15.448Z (10 months ago)
- Topics: dependencies, graph, networkx, python
- Language: Python
- Homepage:
- Size: 109 KB
- Stars: 19
- Watchers: 4
- Forks: 3
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- Contributing: docs/contributing.rst
- License: LICENSE
Awesome Lists containing this project
README
# Depx
[](https://travis-ci.org/tilboerner/depx)
Examine and visualize dependencies used by Python modules.
This is a simple, exploratory prototype for now. The goal is to use explicit
`import` statements in a module to identify the names of its dependencies. This
will not always produce a complete picture of all other code a module uses,
since there is a multitude of ways to import or reference other code
dynamically. Idiomatic Django, for example, uses a number of them. Those are
all out of scope, however, although some might get considered at a later time.
In this early stage, all functionality, structure and interfaces are subject to
radical and surprising changes.
## Dev setup
You're going to need [Poetry](https://python-poetry.org/) and
[tox](http://tox.readthedocs.org/).
After cloning the repo, set up the dev environment:
$ cd depx
$ poetry install --no-root
Run tests:
$ make test
Lint:
$ make lint
Comprehensive test suite:
$ tox
Add dependencies:
$ poetry add [--dev]
## Envisioned use cases
The project should enable the following use cases, but might do so by handing
off the right kind of data to other software. If we do different things
ourselves, they should end up in different commands (or at least subcommands).
* visualize dependencies of module, package or project
* identify dependency cycles
* help identify unused dependencies
## Existing and potential functionality
Sketch of ideas. This is not meant as a plan, but to guide initial development.
### Find dependencies
- [x] identify all explicit imports a module makes
- [x] same for whole packages
- [x] same for arbitrary directories
- [x] identify local imports (those are smelly)
- [ ] distinguish built-in, 3rd party and local dependencies
### Names
- [x] show fully qualified names for importing module and dependency
- [x] ability to show only top-level names
- [x] resolve relative imports to proper names
- [ ] resolve `*` imports
### Output formats
depx my-awesome-project --format html
The identified dependencies are the edges of a directed graph. Output formats
should include several standard ways to consume such data.
- [x] JSON
- [x] GraphML
- [x] browser-ready HTML with visualization
- [x] Graphviz (`.dot`)
- [ ] text with columns (to compose with Unix pipes)