rewindpy
PulseGate's liveness check found it on 14 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 6 Aug 2026. How this is checked
rewindpy is a post-crash time-travel debugger for Python that allows developers to step backwards and forwards through program execution after a crash has occurred. It captures execution history to enable inspection of variables, call stacks, and program state at any point leading up to the failure. The tool is designed for Python developers who need advanced debugging capabilities beyond traditional tracebacks.
Inferred · not functionally tested
Overview
5 featuresPurpose: Debugging Python crashes after they have already occurred without needing to reproduce the error.
Inferred · not functionally tested
Audience: Python developers
Inferred · not functionally tested
Functions: Unknown
Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
In the Debugging & profiling space, rewindpy takes a focused approach. Inferred · not functionally tested: It focuses on debugging Python crashes after they have already occurred without needing to reproduce the error. Inferred · not functionally tested: rewindpy is an open-source project aimed at python developers. Basis unknown · not verified: rewindpy is open source under the MIT license. Basis unknown · not verified: rewindpy is available on the command line.
It is developed by LIRuixuan0407, and it first shipped in 2026. The project is developed in the open on GitHub with 28 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include time-travel debugging, post-crash analysis, and execution history capture.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Time-travel debugging
- Post-crash analysis
- Execution history capture
- Variable inspection
- Traceback visualization
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
Frequently asked questions about rewindpy
- What does rewindpy do?
- Inferred · not functionally tested: Rewindpy focuses on debugging Python crashes after they have already occurred without needing to reproduce the error. It is catalogued under Debugging & profiling on PulseGate.
- Who is rewindpy for?
- Inferred · not functionally tested: rewindpy is an open-source project built for python developers.
- Does rewindpy have a free plan?
- Basis unknown · not verified: Yes — rewindpy is open source under the MIT license and free to use.
- What platforms does rewindpy run on?
- Basis unknown · not verified: rewindpy runs on the command line.
- Is rewindpy still active?
- PulseGate's liveness check found it on 14 Oct 2026. Its GitHub repository shows 28 commits in the last 90 days.
- Who develops rewindpy?
- rewindpy is developed by LIRuixuan0407.
- When did rewindpy launch?
- rewindpy first shipped in 2026.
- Is rewindpy open source?
- Basis unknown · not verified: Yes — rewindpy is open source under the MIT license, developed on GitHub.
Similar projects
Closest matches by what these projects do