PyCharm 2020.2.4 Debugger Not Engaging (stuck)
The Issue
I upgraded to 2020.2.4. When I set a breakpoint, the debugger "gets stuck" or doesn't engage the debugger. I haven't had issues with this in the past versions. Please see my image below. I'm usually debugging a Django project. The project below is a regular Python project (a few Python files and some .yaml files). Am I using debugger wrong or is there something I can do to cause debugger to engage at my breakpoints?
Version and System (Windows 10)
PyCharm 2020.2.4 (Professional Edition)
Build #PY-202.8194.15, built on November 25, 2020
You have a perpetual fallback license for this version
Subscription is active until September 29, 2021
Runtime version: 11.0.9+11-b944.49 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1973M
Cores: 8
Registry: documentation.show.toolbar=true, debugger.watches.in.variables=false, ide.tooltip.initialDelay=0, js.debugger.webconsole=false
Non-Bundled Plugins: com.floobits.unique.plugin.id, mobi.hsz.idea.gitignore, com.jetbrains.codeWithMe, org.nik.presentation-assistant, ua.in.dej.myEmmet, com.jetbrains.intellij.datalore, net.fhtagn.pycharm.cellmode
Picture
请先登录再写评论。
I find the debugger DOES engage IF I call the class method within the script (ex: adz.get_campaigns() is literally written and called in my file - main.py - instead of calling in the interpreter).
Is it not possible to set a break point, then try to call the class method to engage the debugger at the desired breakpoint when working interactively with the Python Console? Hope that doesn't come off sounding condescending; I really don't know.
Thanks a ton!
Seems to be a bug indeed. I created a ticket in our bug tracker for a responsible developer to investigate https://youtrack.jetbrains.com/issue/PY-46014 Please follow it for updates and feel free to comment there.