First off, thank you for these great comments, I’ll try to address them one by one:
I was under the impression that the pdb quit would stop the whole process, but I did a few tests and it looks like it’s not the case when running within a Kernel, which is great news. I’ll try to implement the quit button, and if it works ok, I’ll publish it with the next release of PixieDust.
Let’s take this thread to GitHub: https://github.com/ibm-watson-data-lab/pixiedust/issues/689
Oh I see, sorry, this feature is not yet implemented. Right now PixieDebugger is using the standard python pdb package. I’m planning rewrite PixieDebugger by extending the pdb class, only then will I be able to implement an abort functionality and many more functionalities I have in mind.
Yes, I mention in the article that you have to make sure the debugger has stopped running until you can run another cell, as once a debugging session has started, the kernel is suspended. As a side effect, If you re-run the same cell before the debugger has finished, the debugger UI is gone and you won’t be able to make the Notebook responsive again…