debug-dojo 0.9.0__tar.gz → 0.10.0__tar.gz

debug_dojo-0.10.0/.coveragerc

@@ -0,0 +1,41 @@
+[run]
+branch = true
+# core = sysmon
+patch =
+    subprocess
+    _exit
+source =
+    src/debug_dojo
+    tests
+omit =
+    */__snapshots__/*
+    */site-packages/*
+    */tests/assets/*
+
+[report]
+show_missing = true
+skip_covered = false
+skip_empty = true
+fail_under = 100
+exclude_also =
+    pragma: no cover
+    def __repr__
+    if self\.debug:
+    raise AssertionError
+    raise NotImplementedError
+    return NotImplemented\b
+    if 0:
+    if __name__ == .__main__.:
+    if TYPE_CHECKING:
+    class .*\bProtocol\):
+    @(abc\.)?abstractmethod
+    @overload
+    @(typing\.)?overload
+    (typing\.)?assert_never
+    \.\.\.
+
+[html]
+directory = htmlcov
+
+[xml]
+output = coverage.xml

debug_dojo-0.10.0/.zizmor.yml

@@ -0,0 +1,3 @@
+rules:
+    unpinned-uses:
+        disable: true

{debug_dojo-0.9.0 → debug_dojo-0.10.0}/LICENSE

@@ -1,6 +1,6 @@
-# The MIT License (MIT)
+MIT License
 
-Copyright (c) 2025 to bwrob.
+Copyright (c) 2026 bwrob
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

debug_dojo-0.10.0/PKG-INFO

@@ -0,0 +1,149 @@
+Metadata-Version: 2.4
+Name: debug-dojo
+Version: 0.10.0
+Summary: 🏣 debug dojo, a place for zen debugging
+Author: bwrob
+Author-email: bwrob <bartosz.marcin.wroblewski@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Software Development :: Debuggers
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Dist: ipython>=9.0.0
+Requires-Dist: rich>=15.0.0
+Requires-Python: >=3.12
+Project-URL: Documentation, https://bwrob.github.io/debug-dojo/
+Project-URL: Homepage, https://github.com/bwrob/debug-dojo
+Project-URL: Issues, https://github.com/bwrob/debug-dojo/issues
+Project-URL: Repository, https://github.com/bwrob/debug-dojo.git
+Description-Content-Type: text/markdown
+
+#
+
+<p align="center">
+  <img src="https://github.com/bwrob/debug-dojo/blob/main/docs/logo/banner.png?raw=true" alt="debug dojo" style="width:100%;"/>
+</p>
+
+<p align="center">
+<em>🏣 debug dojo, a place for zen debugging</em>
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/debug-dojo">
+    <img src="https://img.shields.io/pypi/v/debug-dojo.svg?style=flat-square" alt="PyPi Version">
+  </a>
+  <a href="https://pypi.org/pypi/debug-dojo/">
+    <img src="https://img.shields.io/pypi/pyversions/debug-dojo.svg?style=flat-square" alt="PyPI pyversions">
+  </a>
+  <a href="https://pepy.tech/project/debug-dojo">
+    <img src="https://static.pepy.tech/badge/debug-dojo/month" alt="downloads">
+  </a>
+  <a href="https://github.com/bwrob/debug-dojo/blob/main/LICENSE">
+    <img src="https://img.shields.io/github/license/bwrob/debug-dojo.svg" alt="license">
+  </a>
+  <a href="https://results.pre-commit.ci/latest/github/bwrob/debug-dojo/main">
+    <img src="https://results.pre-commit.ci/badge/github/bwrob/debug-dojo/main.svg" alt="pre-commit.ci status">
+  </a>
+</p>
+
+[**debug-dojo**](https://bwrob.github.io/debug-dojo/) is a standalone,
+zero-configuration Python debugger and runner built around `dpdb`—an IPython-powered
+interactive debugger with [`rich`](https://github.com/Textualize/rich) terminal panels,
+inline variable diffs, and built-in object inspection.
+
+## ✨ Features
+
+- **Zero-Install & Zero-Config:** Run any script directly with
+  `uvx debug-dojo script.py`. Automatically discovers your project's `.venv` and leaves
+  no configuration, cache, or history files behind.
+- **Opinionated `dpdb` Debugger:** Combines IPython tab completion and syntax
+  highlighting with Rich tables (`w`, `a`, `b`, `display`, `h`), panels (`whatis`,
+  `psource`, `pinfo`), adaptive source context, and an inline frame context banner
+  (`Δ Changed`, `↳ Line`, `↩ Return`, `👁 Watch`).
+- **Automatic Post-Mortem:** Unhandled exceptions render a Rich traceback and drop
+  directly into a `dpdb` post-mortem session at the failing frame.
+- **Built-in Inspection Shortcuts:** Injects `b()` (breakpoint), `p(obj)` (Rich print),
+  `i(obj)` (Rich inspect), and `c(obj1, obj2)` (side-by-side comparison) into
+  `builtins`.
+
+## 🚀 Quick Start
+
+Run any Python script directly with `uvx`:
+
+```bash
+uvx debug-dojo my_script.py
+```
+
+Or install `debug-dojo` into an environment with `uv`:
+
+```bash
+uv pip install debug-dojo
+```
+
+## 💻 CLI Usage
+
+Run a Python script, executable command, or module directly with `debug-dojo` (or the
+`dojo` alias), optionally seeding breakpoints from the command line without editing the
+file:
+
+```console
+debug-dojo my_script.py arg1 arg2
+debug-dojo -b 42 -b process_data my_script.py
+debug-dojo pytest -k test_feature
+debug-dojo my_package.my_module
+```
+
+## 🐍 Usage in Code
+
+Import `debug_dojo.install` in your Python code to configure `dpdb` and inject helpers
+(`b`, `p`, `i`, `c`) into `builtins`:
+
+```python
+import debug_dojo.install
+
+object_1 = {"foo": 1, "bar": 2}
+object_2 = [1, 2, 3]
+
+# Pretty print an object with Rich
+p(object_1)
+
+# Inspect an object using Rich
+i(object_1)
+
+# Compare two objects side-by-side
+c(object_1, object_2)
+
+# Enter the dpdb debugger
+# b()
+```
+
+Or use the standard `pdb` / `ipdb`-compatible top-level functions and
+`PYTHONBREAKPOINT` hook directly:
+
+```python
+import debug_dojo
+
+debug_dojo.set_trace()
+# debug_dojo.post_mortem()
+# debug_dojo.pm()
+```
+
+## 📚 Documentation
+
+For CLI flags, `dpdb` interactive commands, and API reference, visit the
+[official documentation](https://bwrob.github.io/debug-dojo/).
+
+## 🤝 Contributing
+
+Contributions are welcome! Refer to the
+[development guidelines](https://bwrob.github.io/debug-dojo/getting-started/#development-workflow)
+for instructions on setting up the development environment and running verification
+checks.

debug_dojo-0.10.0/README.md

@@ -0,0 +1,121 @@
+#
+
+<p align="center">
+  <img src="https://github.com/bwrob/debug-dojo/blob/main/docs/logo/banner.png?raw=true" alt="debug dojo" style="width:100%;"/>
+</p>
+
+<p align="center">
+<em>🏣 debug dojo, a place for zen debugging</em>
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/debug-dojo">
+    <img src="https://img.shields.io/pypi/v/debug-dojo.svg?style=flat-square" alt="PyPi Version">
+  </a>
+  <a href="https://pypi.org/pypi/debug-dojo/">
+    <img src="https://img.shields.io/pypi/pyversions/debug-dojo.svg?style=flat-square" alt="PyPI pyversions">
+  </a>
+  <a href="https://pepy.tech/project/debug-dojo">
+    <img src="https://static.pepy.tech/badge/debug-dojo/month" alt="downloads">
+  </a>
+  <a href="https://github.com/bwrob/debug-dojo/blob/main/LICENSE">
+    <img src="https://img.shields.io/github/license/bwrob/debug-dojo.svg" alt="license">
+  </a>
+  <a href="https://results.pre-commit.ci/latest/github/bwrob/debug-dojo/main">
+    <img src="https://results.pre-commit.ci/badge/github/bwrob/debug-dojo/main.svg" alt="pre-commit.ci status">
+  </a>
+</p>
+
+[**debug-dojo**](https://bwrob.github.io/debug-dojo/) is a standalone,
+zero-configuration Python debugger and runner built around `dpdb`—an IPython-powered
+interactive debugger with [`rich`](https://github.com/Textualize/rich) terminal panels,
+inline variable diffs, and built-in object inspection.
+
+## ✨ Features
+
+- **Zero-Install & Zero-Config:** Run any script directly with
+  `uvx debug-dojo script.py`. Automatically discovers your project's `.venv` and leaves
+  no configuration, cache, or history files behind.
+- **Opinionated `dpdb` Debugger:** Combines IPython tab completion and syntax
+  highlighting with Rich tables (`w`, `a`, `b`, `display`, `h`), panels (`whatis`,
+  `psource`, `pinfo`), adaptive source context, and an inline frame context banner
+  (`Δ Changed`, `↳ Line`, `↩ Return`, `👁 Watch`).
+- **Automatic Post-Mortem:** Unhandled exceptions render a Rich traceback and drop
+  directly into a `dpdb` post-mortem session at the failing frame.
+- **Built-in Inspection Shortcuts:** Injects `b()` (breakpoint), `p(obj)` (Rich print),
+  `i(obj)` (Rich inspect), and `c(obj1, obj2)` (side-by-side comparison) into
+  `builtins`.
+
+## 🚀 Quick Start
+
+Run any Python script directly with `uvx`:
+
+```bash
+uvx debug-dojo my_script.py
+```
+
+Or install `debug-dojo` into an environment with `uv`:
+
+```bash
+uv pip install debug-dojo
+```
+
+## 💻 CLI Usage
+
+Run a Python script, executable command, or module directly with `debug-dojo` (or the
+`dojo` alias), optionally seeding breakpoints from the command line without editing the
+file:
+
+```console
+debug-dojo my_script.py arg1 arg2
+debug-dojo -b 42 -b process_data my_script.py
+debug-dojo pytest -k test_feature
+debug-dojo my_package.my_module
+```
+
+## 🐍 Usage in Code
+
+Import `debug_dojo.install` in your Python code to configure `dpdb` and inject helpers
+(`b`, `p`, `i`, `c`) into `builtins`:
+
+```python
+import debug_dojo.install
+
+object_1 = {"foo": 1, "bar": 2}
+object_2 = [1, 2, 3]
+
+# Pretty print an object with Rich
+p(object_1)
+
+# Inspect an object using Rich
+i(object_1)
+
+# Compare two objects side-by-side
+c(object_1, object_2)
+
+# Enter the dpdb debugger
+# b()
+```
+
+Or use the standard `pdb` / `ipdb`-compatible top-level functions and
+`PYTHONBREAKPOINT` hook directly:
+
+```python
+import debug_dojo
+
+debug_dojo.set_trace()
+# debug_dojo.post_mortem()
+# debug_dojo.pm()
+```
+
+## 📚 Documentation
+
+For CLI flags, `dpdb` interactive commands, and API reference, visit the
+[official documentation](https://bwrob.github.io/debug-dojo/).
+
+## 🤝 Contributing
+
+Contributions are welcome! Refer to the
+[development guidelines](https://bwrob.github.io/debug-dojo/getting-started/#development-workflow)
+for instructions on setting up the development environment and running verification
+checks.