Added developer debugging tools (#1479) #1508
Conversation
pycharm_debugger.py
Outdated
| port=12345, # Use the same port number configured in PyCharm | ||
| stdoutToServer=True, | ||
| stderrToServer=True, | ||
| # suspend=True |
There was a problem hiding this comment.
What's this option for?
There was a problem hiding this comment.
Good point, I've changed that now so it's set better. suspend=True means it stops at breakpoint().
What's really annoying is that by default (suspend=True) the context in your IDE gets moved to this module which takes you away from the code you want to be looking at.
Explicitly setting suspend=False (as I've done now) stops that, it now only stops at the breakpoints set in the gutter.
I've also added an image for the matching pycharm configuration to the docs.
| @@ -0,0 +1,3 @@ | |||
| -c requirements.txt | |||
| django-debug-toolbar | |||
| pydevd-pycharm==242.23726.102 # pinned to appropriate version for current pycharm | |||
There was a problem hiding this comment.
I can see the argument for pinning this. I can also see an argument for leaving it unconstrained. Either way requires action when any team member upgrades.
There was a problem hiding this comment.
I'd prefer to not pin it, but it's required that it's pinned at the moment.
The issue is pycharm is very picky about the version of pydevd-pycharm it'll work with at any point in time, and as a good example of this, when I first set this up there was a newer version of pydevd-pycharm, but it wasn't compatible with the current version of pycharm and pycharm will complain if you use it... ¯\_(ツ)_/¯
I see now they released another version 2 hours ago so I'll test if that works soon but for now this is compatible.
daveoconnor
force-pushed
the
doc/1479-debug-tools
branch
from
c55c35c
to
f233f27
Compare
This adds django debug toolbar and a framework for support for debuggers, with a pycharm setup.