Bug report

Consider the following structure:
a.py (foo())
'- b.py (bar())
meaning that a.py with foo() calls some function from b.py, namely bar().

Now, add a breakpoint to b.py and let the debugging begin. You will see that the debugger seems to simply overlook the breakpoint in b.py. In other words: Breakpoints are only accepted, if the next line to be executed before clicking on "Go" is in the same file.

This is rather bothersome and does work correctly in other IDEs like Qt for C++.

The solution

Please "step down" to a breakpoint by design.

Your environment

• CPython versions tested on: 3.11.1
• Operating system and architecture: Windows 10