Hi HN!<p>We just released debuglater (<a href="https://github.com/ploomber/debuglater" rel="nofollow">https://github.com/ploomber/debuglater</a>), an open-source library that serializes a Python traceback object for later debugging.<p>You can see a quick video demo here: <a href="https://github.com/ploomber/debuglater/blob/master/README.md" rel="nofollow">https://github.com/ploomber/debuglater/blob/master/README.md</a><p>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.<p>We built this to support our open-source framework for data scientists (<a href="https://github.com/ploomber/ploomber" rel="nofollow">https://github.com/ploomber/ploomber</a>), 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!<p>The implementation is quite interesting. You can see it here (<a href="https://github.com/ploomber/debuglater/blob/master/src/debuglater/pydump.py" rel="nofollow">https://github.com/ploomber/debuglater/blob/master/src/debug...</a>). 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!<p>Please take it for a spin and let us what you think!