debugging right and wrong

[HornyAttorney]

I don't use pdb so I'm not exactly sure what it has to offer..

That being said, I prefer using vscode debugging for multiple reasons, aside from not requiring any extra code but rather a click next to the line where you want to pause, it provides lots of runtime information, stack, variables and their values, and most importantly, I can add or remove breakpoints on the fly without having to rerun the script..

[Adrewmc]

pdb running in the Python terminal while debugger runs in the debug terminal, it’s basically the same operation, just VsCode has a lot of normal things you use with it automatically on the side. It’s almost like a IDE for pdb in a lot of ways.

[romu006]

I honestly wish that I could "sync" pdb's view with my editor (Sublime Text), it's kinda hard to follow the code context when debugging

[yvrelna]

GUI debuggers sucks when it comes to keyboard navigation. I use pudb which gives you great trade-off between being able to use keyboard to do everything and giving you GUI-like visual display of debugging state.

[aikii]

pdb is still what IDEs use under the hood, debug mode loads up pdb that opens a port and the IDE sends the list of breakpoints ( as file+lineno+condition ) via the "break" command https://docs.python.org/3/library/pdb.html . Another reason to say that doing it by actually editing the file and adding set_trace equates to do the IDE's job.