Debug mode

[vangberg]

Executive Summary

Proposal for "debug mode" to capture runtime function execution context (parameters, globals) using Python's trace module (1), enabling iterative development on function bodies as isolated scripts within pdit workflow (1). Motivated by author's experience converting Python packages to scripts for pdit compatibility (1). No implementation discussion or consensus yet; issue remains exploratory (1).

Key Technical Points

• Would leverage Python's trace module or similar tooling to capture function execution state (1)
• Explicit breakpoints proposed as potential mechanism for capturing function context (1)
• Return values would be displayed in outputs for validation against expectations (1)
• Enables treating function bodies as flat scripts, eliminating need to convert packages to scripts (1)
• Related to issue Function execution #21 (1)

Action Items

• No concrete implementation steps or discussion participants beyond author; awaiting community feedback (1)

---

Generated on 2025-12-15 09:38:09 by Issuerizer

[vangberg]

Crazy idea. I recently converted a Python package to a script, so I could use pdit to work on it. A "debug mode" would use trace or something like it to "capture" what happens in a function at runtime (or maybe you explicitly set a breakpoint). The idea is to be able to "focus" on a function that is called with a specific set of parameters and specific set of globals - essentially acting as if the function was a flat script. This would allow you to iterate on the function body using pdit, changing the code until the return value (which would also be visible in the outputs) matches your expectation.

Related to #21