News for hackers. Stuff that matters.

A comment on PySnooper: Never use print for debugging again. Parent comment

Re:PySnooper: Never use print for debugging again by hguhghuff on Monday April 22, 2019 @07:21AM (#19717995)
On the contrary I think the author is spot on. I can never be bothered to get the debugger going no matter how easy.
[ Parent | on HN ]
Re:PySnooper: Never use print for debugging again by hobs on Monday April 22, 2019 @10:02AM (#19718971)
So why would installing another debugger be easier?
[ Parent | on HN ]
Re:PySnooper: Never use print for debugging again by apetresc on Monday April 22, 2019 @10:06AM (#19719016)
But this isn't a debugger. It's just instrumenting a function with some very verbose logs.
[ Parent | on HN ]
Re:PySnooper: Never use print for debugging again by stefano on Monday April 22, 2019 @10:47AM (#19719313)
But it's harder to install this, import it, and add a decorator than it is to type "breakpoint()".
[ Parent | on HN ]
Re:PySnooper: Never use print for debugging again by scbrg on Monday April 22, 2019 @04:32PM (#19722661)
It might be easier than migrating to 3.7, and then typing "breakpoint()"
[ Parent | on HN ]
Re:PySnooper: Never use print for debugging again by skybrian on Monday April 22, 2019 @01:15PM (#19720664)
That requires an interactive session, for example starting the program yourself from the command line.
[ Parent | on HN ]