Debugger step over works differently in 2016.2
Answered
I had 2016.1.2, updated to 2014.1.4 then to 2014.2.
Somewhere along the way my debugger started working slightly differently from previous versions.
Say I have the following code with a break point on line 9 and start stepping over (F8) the code. Once I get to line 12, I expect the step to continue in foo() at line 4 on to line 5, 6, then to 15,16.
Unfortunately this is not the case anymore. After line 12, the step will go to line 4, then continue on with the rest of the program. Is there some setting that controls how this works?
Please sign in to leave a comment.
Yes, I've spotted the problem. Please, go to Python Debugger settings (https://www.jetbrains.com/help/pycharm/2016.2/python-debugger.html) and uncheck the option "Collect run-time types information for code insight". Does it help?
It's a bug and I've created the issue about it in our tracker: https://youtrack.jetbrains.com/issue/PY-20335
Hi Marcel Wilson! Unfortunately, I can't reproduce the bug. For me the debugger after line 12 goes to line 5, 6 and then to line 16.
Please, set environment variable PYCHARM_DEBUG=True to your run configuration and provide console output for your debug session.
uncheck the option "Collect run-time types information for code insight". Does it help?
I'll be darned, that was it!
I want to make sure I understand the ramifications of this. That setting is what allows me to see type hinting automatically in the editor if I haven't used restructured text in the docstring yet, right? (i.e. when I use ctrl+q to see quick-documentation) So using docstring type hinting will still work, I just won't get the automatically determined hints at run-time. I think I can live with for now.
Thanks for the help!