🏣 debug dojo, a place for zen debugging
debug-dojo is a powerful Python package designed to streamline your debugging workflow directly from the terminal. It integrates seamlessly with popular debuggers and enhances your inspection capabilities with beautiful, readable output.
✨ Features
- Unified Debugging Interface: Easily launch your scripts or modules with your preferred debugger (
debugpy,pudb,pdb,ipdb). - Dojo Belts Gamification: Earn belts based on your debugging experience and track your progress.
- Enhanced Output with Rich: Leverages
richfor stunning, syntax-highlighted code, pretty-printed objects, and improved tracebacks. - Side-by-side Object Comparison: Quickly identify differences between two Python objects.
- Interactive Object Inspection: Dive deep into object structures with a powerful
inspectutility. - Simplified Breakpoints: Set breakpoints effortlessly with a concise helper function.
🚀 Installation
Install debug-dojo using pip:
pip install debug-dojo
For full debugger support, you might want to install optional dependencies:
pip install "debug-dojo[all-debuggers]"
💻 CLI Usage
Run your Python script or module with dojo run:
dojo run my_script.py
Check your progress and current belt with:
dojo belt
Specify a debugger, configuration file, or enable verbose output:
dojo run --debugger ipdb --config dojo.toml --verbose --module my_module
Run an executable command with debugging tools:
dojo run --exec pytest
🐍 Usage in Code
Integrate debug-dojo directly into your Python code for on-demand debugging and inspection utilities:
import debug_dojo.install
# Set a breakpoint and enter the debugger
# debug_dojo.install.b() # Equivalent to breakpoint()
object_1 = {"foo": 1, "bar": 2}
object_2 = [1, 2, 3]
# Pretty print an object with Rich
debug_dojo.install.p(object_1)
# Inspect an object using Rich
debug_dojo.install.i(object_1)
# Compare two objects side-by-side
debug_dojo.install.c(object_1, object_2)
# Enter the debugger (e.g., ipdb, pudb, pdb, debugpy based on config)
# debug_dojo.install.b()
📚 Documentation
For comprehensive instructions on installation, configuration, advanced usage, and API reference, please visit the official documentation.
🤝 Contributing
Contributions are welcome! Please refer to the development guidelines for details on how to set up your development environment and submit changes.
Metadata
Release files for debug-dojo 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| debug_dojo-0.9.0.tar.gz | 21.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| debug_dojo-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.1 kB
Release files / debug_dojo-0.9.0.tar.gz
| Download URL | debug_dojo-0.9.0.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1152b1ec39a5a594fa4506b0e18d32a73f250d93252282dcf6fb0ae38d485655
|
|
BLAKE2b-256 checksum How to use checksums |
124d61f8d8e9802e2ff39c6def2590d184d175d771386eb8d03780ebf26dc1ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2026.
Transparency logRelease files / debug_dojo-0.9.0-py3-none-any.whl
| Download URL | debug_dojo-0.9.0-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77920f61ce86d7de56567606f78f24aa5dfc77f175e8b25b3246035a2703be03
|
|
BLAKE2b-256 checksum How to use checksums |
92074dd8b258995558fb9fd3a946fcc70e08f02094b9a073ea6047262621fd16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2026.
Transparency log