I wonder, when you already run this within PyCharm, why not just set breakpoints and use the PyCharm debugger?
It's not just PyCharm. A debugger can be set up in many other development environments, but it seems some people refuse to use a debugger. I've seen this more in the PHP community, where people swear that they'll never use a debugger and say there's no need to learn because putting `var_dump` everywhere is better.
For sure, packages like these have their places, but if you're using it for debugging, you're doing software development wrong.
I can sympathize, though, with situations like trying to use a remote debugger when there's a distributed backend of php services. In that case, your var_dump gets distributed everywhere too, so you don't need to chase where the request went to.
Comments
It's not just PyCharm. A debugger can be set up in many other development environments, but it seems some people refuse to use a debugger. I've seen this more in the PHP community, where people swear that they'll never use a debugger and say there's no need to learn because putting `var_dump` everywhere is better.
For sure, packages like these have their places, but if you're using it for debugging, you're doing software development wrong.
I can sympathize, though, with situations like trying to use a remote debugger when there's a distributed backend of php services. In that case, your var_dump gets distributed everywhere too, so you don't need to chase where the request went to.
For me, unit tests is what's replaced the debugger.
I still try to fire up the PyCharm debugger sometimes, but setting up the environment usually proves too hard.