ipdb VS pudb

Why not just use Python’s built-in pdb debugger or another existing one like ipdb or pdbpp?

Unfortunately, I couldn't find any official documentation. But here is a small cheatsheet about it and here is there is github repo.

Integration of IPython pdb

One thing I have used is drop into the Python debugger (also ipdb) from within a signal handler. Then I can run a kill, and have it drop into the debugger.

There are some of cute hacks to get a remote debugger which I haven't used in years.

https://github.com/sassoftware/epdb can start and connect to a remote debug instance

https://github.com/gotcha/ipdb

Now tie in some ipdb [1] and you have a pretty sweet setup. Also depending on your serving framework it might also have hot reloading as well, tornado, flask, etc.

[1]https://github.com/gotcha/ipdb

[2] https://www.tornadoweb.org/en/stable/autoreload.html https://werkzeug.palletsprojects.com/en/0.14.x/serving/

I simply use the superb pudb. Press ctrl+e to open the current file at the current line in your editor.

such a waste of time...

To this day, I'm baffled by the dynamic language folks who cannot get they head around how strictness/rigor (via a good expressive type system) actually makes maintenance easier and more importantly: cheaper.

[1] https://github.com/inducer/pudb

I use the very under-rated pudb in an adjacent terminal window.

I've been using PuDB for a while now.

I think it is also worth mentioning pudb here

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.

For a quick view etc I usually fire up pudb in an adjacent terminal window but for a detailed/heavy debugging session I fire up VS Code (with the vim plugin of course). I have used vi/vim for 37+ years now so it is part of my DNA and use VS Code only for it's great vim + debugging facility.

Two that I haven’t seen here and have saved me tons of time are pudb, a great debugger and petl a simple powerful ETL toolkit.

If you want to debug Python then pudb is simply superb. Vim users don't really want or need to "debug inside of vim" do they? We usually are happy to use multiple command line and other tools in adjacent windows. Also, you can just step around and view variables etc in pudb and then press ctrl+e to edit that file in vim, then q to restart debugger.