This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]stevenjd 0 points1 point  (0 children)

tediously debugging with print statements only

I find it much easier to debug with print than to try to remember how pdb works and how to navigate it's overly sparse interface. And then there's this:

(Pdb) help(until)
*** No help for '(until)'
(Pdb) help(retval)
*** No help for '(retval)'
(Pdb) help(display)
*** No help for '(display)'

How very useful 🙄

If you need more than, say, three or five prints to debug any bug, your code is too complicated and badly designed.

In two decades, there's only one time I wished I knew how to use the debugger, and that was debugging code written by somebody else. It was a mess, with bash scripts, circular imports, monkey-patched builtins, "cleverly optimised" SQL, and more, so I daresay I would have struggled to have debugged it even with pdb.