What happened inside your Python execution? Ormaos records it so your coding agent can read what actually ran. Open source, Python 3.12+. Coming November 2026.
4 comments
The plan is to record a Python execution (the call tree of your own code, every exception including the swallowed ones, and the exact lines that ran in a function you scope) so a coding agent can query it from the terminal.
Any feedback helps, whether the problem is real for you, what's unclear on the page, any questions, or why you think it wouldn't work. And if something like this already exists for Python, please tell me.
For feedback on an idea, a blog post might work.
But in all of this, using HN solely or mostly for self-promotion is not consistent with the guidelines.
The HN guidelines are linked on the bottom of HN pages and if you aren't clear on something, you can contact the moderators using the contact link at the bottom of the page -- that's what they are here for.
Good luck.
Read the full thread on Hacker News →
Related stories
- Hacker News · 2 points · about 15 hours ago
- DEV Community · 13 points · 7 days ago
- Lobsters · 22 points · about 10 years ago
- Lobsters · 10 points · 6 months ago
- yieldfrom 1.0.0: A backport of the `yield from` semantic from Python 3.x to Python 2.7pypi.python.orgLobsters · 11 points · over 9 years ago
- Jubilant: Python subprocess and Go codegenbenhoyt.comLobsters · 14 points · 10 months ago