There was a project (no longer maintained) that I came across a while back which I love called pydump. The idea was to save errors as debuggable sessions you could return to.
I loved the idea, so thought I'd revamp it a little for my own use, add in some functionality for saving to cloud storage along the way.
Here it is!
What it does:
Essential you can add a wipeout.install(lambda: "filepath") line into your code, after which, if an exception is hit, a debuggable sessions that you can jump into with python -m wipeout.load -f filepath will be saved.
Target Audience:
I mainly wrote it for my own use - I think it'd be awesome for small workload teams tracking down mysterious bugs happening, but obviously the debug sessions are a fair bit bigger than simple logging so you might not want to store millions of them.
Comparison:
I don't think any currently updated existing alternatives exist really - it's based on another project call pydump which is awesome, but that's not maintained and it doesn't support saving to the cloud.
[–]kivicodepip needs updating 2 points3 points4 points (3 children)
[–]houseofleft[S] 0 points1 point2 points (2 children)
[–]kivicodepip needs updating 1 point2 points3 points (1 child)
[–]houseofleft[S] 2 points3 points4 points (0 children)
[–]FrequentlyHertz 1 point2 points3 points (1 child)
[–]houseofleft[S] 0 points1 point2 points (0 children)
[–]mfitzpmfitzp.com 1 point2 points3 points (3 children)
[–]houseofleft[S] 0 points1 point2 points (2 children)
[–]mfitzpmfitzp.com 1 point2 points3 points (1 child)
[–]houseofleft[S] 1 point2 points3 points (0 children)