ipdb VS jurigged

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/

If that interests you, I made a package called jurigged that basically does autoreload but asynchronously on Python in general (i.e. you can write jurigged script.py instead of python script.py; it works in a separate thread and can also work in notebooks). It's more surgical than what the notebook does in that it only hot swaps code in changed functions and does not re-execute anything else. This feature is cool too, IMO.

Some of the basic hot-loading features can probably be approximated in Python. Here's some from my bookmarks(i've not tried them personally)

- https://github.com/breuleux/jurigged

- https://github.com/reloadware/reloadium

I would imagine lisp can do this on a whole different level. Emacs seems like a testament to that. Basically the entire editor feels like eval()

I've been using jurigged [0] for hot code reloading which is great. It works by replacing code objects in place at the function level which naturally handles many cases like applying to existing objects, avoiding loading a module multiple times, etc. As others noted the actual source of this one is not there so it's hard to know what it's doing. The published package contains a binary shared library so I suppose it's written as a CPython extension.

[0] https://github.com/breuleux/jurigged