idea 11 python debugging: not catching breakpoints w/o manual setting?

Does idea 11 catch breakpoints in python?  I'm comparing it with PyCharm, and I notice that the pycharm debug startup AUTOMATICALLY adds a "--noreload" option EVEN THOUGH I do not have that checkbox checked.  When I check the box manually in Idea 11, breakpoints start getting caught.  

Is this is a bug?  for debugging, that '--noreload' option is required?

IDEA STARTUP (without checkbox checked)

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw2.7 "/Users/lhamel/Library/Application Support/IntelliJIdea11/python/helpers/pydev/" --multiproc --client --port 49597 --file runserver
No handlers could be found for logger "pydev"
pydev debugger: process 5315 is connecting
Connected to pydev debugger (build 111.167)
Validating models...

PYCHARM STARTUP (without checkbox checked)

Connected to pydev debugger (build 107.576)
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 /Applications/PyCharm --client --port 65500 --file mmsite/ runserver --noreload
pydev debugger: starting
Validating models...

When you don't enable the --noreload option, Django runs two processes for your server - one to watch for changed files and another to serve requests. PyCharm 1.5 (which is what you're using) couldn't handle that in the debugger, so it automatically added --noreload to force running Django as a single process. PyCharm 2.0, as well as the plugin for IntelliJ IDEA 11, are (or at least are supposed to be) capable of debugging multiple processes in one debug session, so they don't set --noreload automatically. However, I don't know why debugging doesn't work for you in this mode. It's possible that this was already fixed but not released in an update of the Python plugin yet.


That helps me understand the underlying reasoning.

Can someone there try debugging with the python plugin?


Please sign in to leave a comment.