PySnooper
snoop
Our great sponsors
| PySnooper | snoop | |
|---|---|---|
| 7 | 4 | |
| 15,077 | 769 | |
| - | - | |
| 4.1 | 5.4 | |
| 3 months ago | 3 months 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.
PySnooper
-
“I think the vast majority of developers still debug using print() statements”
Shameless plug: PySnooper is a debugging tool for Python that lets you debug in a way that's as easy as adding print statements, but gives you a lot more information automatically.
-
Top python libraries/ frameworks that you suggest every one
snoop or pysnooper
-
No more Print For Debugging In Python Anymore
If you want to install a library, pysnooper is cool. It's like an automatic print on every line of your function, with values.
-
The unreasonable effectiveness of print debugging
The Python package PySnooper is pretty good for "fancy" print debug statements: https://github.com/cool-RR/pysnooper
I've caught quite a few bugs using this show-me-all-locals() approach...
- What tool you discovered/came across that has made your development work easier?
-
Icecream: Never use print() to debug again in Python
Funny, a few months back I added this sentence to PySnooper's readme:
"PySnooper is a poor man's debugger. If you've used Bash, it's like set -x for Python, except it's fancier."
snoop
-
Top python libraries/ frameworks that you suggest every one
snoop or pysnooper
-
Stop Using print() for Debugging When You Can Snoop Instead
We have all used strategic print() statements in our code to make sure our code is running a certain line or to see the value of a variable. This gets a little sloppy and doesn't provide much context into why some code is not behaving as expected. Enter snoop, the super dead simple way to see exactly what the code is doing, the line of code that is executing, and when and what the values of local variables are. This can help us understand the flow of our code and identify issues much faster!
-
Icecream: Never use print() to debug again in Python
Try https://github.com/alexmojaki/snoop for both plus more.
What are some alternatives?
python-devtools - Dev tools for python
icecream - 🍦 Never use print() to debug again.
django-modelcluster - Django extension to allow working with 'clusters' of models as a single unit, independently of the database
pdbpp - pdb++, a drop-in replacement for pdb (the Python debugger)
ray - Debug with Ray to fix problems faster
locust - Scalable user load testing tool written in Python
django-hijack-admin - Django admin site integration for Django Hijack
q - Quick and dirty debugging output for tired programmers. ⛺
django-debug-panel - django-debug-toolbar in WebKit DevTools. Works fine with background Ajax requests and non-HTML responses.
rr - Record and Replay Framework