[PR #1571] Added pytrace - Time-Travel Debugger #1368

Open
opened 2025-11-06 13:14:51 -06:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/vinta/awesome-python/pull/1571
Author: @gleb-sevruk
Created: 7/9/2020
Status: 🔄 Open

Base: masterHead: added-pytrace


📝 Commits (1)

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

What is this Python project?

PyTrace is a Record and Replay debugging suite.

It records code execution and variable values at any point of execution. This allows alternative debugging experience, with the ability to step back in the code.

PyTrace UI

What's the difference between this Python project and similar ones?

Usually, profilers only show how long the method run was, without the ability to see actual state of execution.

Also, when debugging unknown or complex code, it is hard to understand the sequence of events and state of variables in the outer scope.

If by some mistake you miss step into some function, you will need to run debugging session again. Using pytrace will allow you to scroll back in time and repeat debugging steps without the need to restart entire thing again.

This tool greatly assists me in regular debugging as it is possible to step back and navigate to the interesting functions via call graph.

As a side effect, graph provides hints regarding the performance implication of each method executed.

Call graph is also using color coding, so each time you record session, files and methods will stay the same color.

Interactive Demo

--

Anyone who agrees with this pull request could submit an Approve review to it.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/vinta/awesome-python/pull/1571 **Author:** [@gleb-sevruk](https://github.com/gleb-sevruk) **Created:** 7/9/2020 **Status:** 🔄 Open **Base:** `master` ← **Head:** `added-pytrace` --- ### 📝 Commits (1) - [`e91c420`](https://github.com/vinta/awesome-python/commit/e91c420ddf810089d2973a95e25ae71218b6cc35) Added pytrace ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description ## What is this Python project? PyTrace is a Record and Replay debugging suite. It records code execution and variable values at any point of execution. This allows alternative debugging experience, with the ability to step back in the code. ![PyTrace UI](https://hsto.org/webt/vp/im/xd/vpimxdvufmcmirahmktwpii79vw.png) ## What's the difference between this Python project and similar ones? Usually, profilers only show how long the method run was, without the ability to see actual state of execution. Also, when debugging unknown or complex code, it is hard to understand the sequence of events and state of variables in the outer scope. If by some mistake you miss step into some function, you will need to run debugging session again. Using pytrace will allow you to scroll back in time and repeat debugging steps without the need to restart entire thing again. This tool greatly assists me in regular debugging as it is possible to step back and navigate to the interesting functions via call graph. As a side effect, graph provides hints regarding the performance implication of each method executed. Call graph is also using color coding, so each time you record session, files and methods will stay the same color. [Interactive Demo](https://app.pytrace.com/?open=v0.1-interactive-demo) -- Anyone who agrees with this pull request could submit an *Approve* review to it. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 13:14:51 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-python#1368