icecream VS remote-pdb

Hey, very useful. Thanks! Similar to ic() for python, but with the nice ability to be used inline.

https://github.com/gruns/icecream

Icecream is great for this. Just calling ic(foo) gives you the same thing on stderr.

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

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.

We also have ice cream

I found icecream in a post on this subreddit and still use it as an alternative to print for debugging.

In the future using something like icecream might be interesting as well.

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