InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
Debuglater Alternatives
Similar projects and alternatives to debuglater
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
debuglater discussion
debuglater reviews and mentions
-
How do you deal with parallelising parts of an ML pipeline especially on Python?
Finally, debugging. If you're running code in sub-processes; debugging becomes a real pain because out of the box, you won't be able to start a debugger in the sub-processes. Furthermore, there's a chance that more than one fails. One solution is to dump the traceback when any sub-process fails, so you can start a debugging sesstion afterward; look at this project for an example.
-
debuglater: dump Python traceback for later debugging
The implementation is quite interesting. You can see it here. The serialization step has two parts: it takes the traceback object and wraps it into a new object so it can be serialized; secondly, it stores the source code so you can debug even if you don't have access to the source code!
-
debuglater: store Python traceback for later debugging
You can see a quick video demo here.
- GitHub - ploomber/debuglater: Store Python traceback for later debugging.
-
Show HN: Debuglater – Serialize Python traceback for later debugging
Hi HN!
We just released debuglater (https://github.com/ploomber/debuglater), an open-source library that serializes a Python traceback object for later debugging.
You can see a quick video demo here: https://github.com/ploomber/debuglater/blob/master/README.md
Countless times, we've scheduled overnight jobs to find out the following day that they failed. While logs are helpful, they are often insufficient for debugging. debuglater allows you to store the traceback object so you can start a debugging session at any moment.
We built this to support our open-source framework for data scientists (https://github.com/ploomber/ploomber), who often execute long-running code in remote environments. However, we realized this could be useful for the Python community, so we created a separate package. This project is a fork of Eli Finer's pydump, so kudos to him for laying the foundations!
The implementation is quite interesting. You can see it here (https://github.com/ploomber/debuglater/blob/master/src/debug...). The serialization step has two parts: it takes the traceback object and wraps it into a new object so it can be serialized; secondly, it stores the source code so you can debug even if you don't have access to the source code!
Please take it for a spin and let us know your feedback. Please share your feedback!
-
debuglater: Serialize Python traceback for later debugging
We just released debuglater, an open-source library that serializes a Python traceback object for later debugging.
- debuglater: Store Python traceback for later debugging. 🐛
-
A note from our sponsor - InfluxDB
www.influxdata.com | 15 Jun 2025
Stats
ploomber/debuglater is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of debuglater is Python.