snoop VS q

pdbpp: Improved pdb boltons: assorted python addtions twisted: event driven networking framework sorcery: Dark magic in python, things know where+how they are being called, helps reducing boilerplate sh: Better alternative for subprocess module, much more pythonic taskipy: npm run scipt_name like functionality snoop: pdb lite, record+replay function steps birdseye: graphical debugger remote-pdb: easy pdb from inside containers typer: wrapper around click for simpler code for CLIs arrow: Always TZ aware datetimes, plus more features more-itertools: more functions for iterators pydantic: data validation + dataclasses loguru: better logging notifiers: sending notifications from python

snoop or pysnooper

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!

Try https://github.com/alexmojaki/snoop for both plus more.

q - Command line csv data manipulation query-like. Python

For python: i specifically recommend https://github.com/zestyping/q a lot, which is like print debugging on steroids:

  All output goes to /tmp/q (or on Windows, to $HOME/tmp/q). You can watch the output with   this shell command while your program is running:

This is similar to an earlier package called "q"[0]

[0] https://github.com/zestyping/q