debuglater
icecream
debuglater | icecream | |
---|---|---|
8 | 41 | |
52 | 8,480 | |
- | - | |
3.8 | 5.4 | |
3 months ago | about 1 month ago | |
Python | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
debuglater
-
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. 🐛
icecream
-
Show HN: Dbg.h: C macro for quick and dirty print debugging
Hey, very useful. Thanks! Similar to ic() for python, but with the nice ability to be used inline.
https://github.com/gruns/icecream
- When you are looking at someone else's code base and you want to make a copy of it to put in a million print statements to understand it, what is good practice in terms of version control and naming the copy?
-
Pythoneers here, what are some of the best python tricks you guys use when progrmming with python
Icecream is great for this. Just calling ic(foo) gives you the same thing on stderr.
- What's you fav ice cream??
-
What Python debugger do you use?
I get around this by using loguru (a wrapper around python's logger), so I get information like the calling function and line number with my debugging statements. I don't use it these days (and actually built something extremely similar around the same time), but icecream is another alternative that facilitates debugging-by-print
- Top 3 hardest things with debugging as a beginner?
-
Does anyone use python debugger?
Most of the time I simply use icecream (a much better version of print()), and sometimes, I use pudb (a visual debugger) for tougher/trickier bugs.
-
Let's do a war
We also have ice cream
-
What is your favorite ,most underrated 3rd party python module that made your programming 10 times more easier and less code ? so we can also try that out :-) .as a beginner , mine is pyinputplus
I found icecream in a post on this subreddit and still use it as an alternative to print for debugging.
-
A script for print debugging python code
In the future using something like icecream might be interesting as well.
What are some alternatives?
ploomber - The fastest ⚡️ way to build data pipelines. Develop iteratively, deploy anywhere. ☁️
pdb++
pout - Python pretty print on steroids
Loguru - Python logging made (stupidly) simple
pystack - 🔍 🐍 Like pstack but for Python!
py-spy - Sampling profiler for Python programs
Laboratory - Achieving confident refactoring through experimentation with Python 2.7 & 3.3+
remote-pdb - Remote vanilla PDB (over TCP sockets).
PySnooper - Never use print for debugging again
pyflame
django-debug-toolbar - A configurable set of panels that display various debug information about the current request/response.
winpdb - Fork of the official winpdb with improvements