Python Debugpy — Debug Python: pdb REPL + debugpy remote (DAP)
Python Debugpy — Debug Python: pdb REPL + debugpy remote (DAP)
Start with meaning, then move to detail.
This lesson explains Python Debugpy — Debug Python: pdb REPL + debugpy remote (DAP) as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Overview, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Python Debugpy — Debug Python: pdb REPL + debugpy remote (DAP) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Debug Python: pdb REPL + debugpy remote (DAP)
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Overview
Read this after the foundation, then connect it to the previous step.
- 04When to Use
Read this after the foundation, then connect it to the previous step.
- 05pdb Quick Reference
Read this after the foundation, then connect it to the previous step.
- 06Recipe 1: Local breakpoint
Read this after the foundation, then connect it to the previous step.
- 07Recipe 2: Launch a script under pdb (no source edits)
Read this after the foundation, then connect it to the previous step.
- 08Recipe 3: Debug a pytest test
Read this after the foundation, then connect it to the previous step.
- 09Recipe 4: Post-mortem on any exception
Read this after the foundation, then connect it to the previous step.
- 10Recipe 5: Remote debug with debugpy (attach to running process)
Finish here to verify the result and special cases.
Copy only after you understand the effect.
Run the code normally. You land at the `breakpoint()` line with full access to locals.
**Don't forget to remove `breakpoint()` before committing.** Use `git diff` or a pre-commit grep:## Recipe 2: Launch a script under pdb (no source edits)## Recipe 3: Debug a pytest test
The hermes test runner and pytest both support this:Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.