Hi, sorry but from the gif I see that it enters runpy.py but you are saying this is not the expected behavior? Could you clarify what you think should happen? What code are you expecting to step into?

The expected behavior is that when I step into the heapify function, my debugger should go into the heapq.py file (the page in the middle of the screen) and go to the first line of the heapify function, where my second breakpoint is.

In addition, because I have a breakpoint in the heapify function that my code uses, stepping over the heapify(l) in my test2.py file should also make it so that the code execution stops at the breakpoint that I have in the heapify function.

The fact that the runpy.py gets opened at the end of the execution of my test2.py file is a result of enabling justMyCode, although it's unwanted.

gotcha, sorry missed that. What python version are you using? If you are using 3.12 could you try a different version as it might be related to this: microsoft/debugpy#1887

This doesn't seem directly related to microsoft/debugpy#1887 - I can reproduce the issue described here on any Python version, not just 3.12+

I have the same issue in a large Django project. I can debug files from my virtual env, but only by first setting a breakpoint in my own code, then stepping into an external function call.

@eleanorjboyd

Apologies for the delay. (Work has got me busy.)

Even if I downgrade my Python interpreter to version 3.9.6 from 3.12.9 (as it was in the gif), the same result happens.

Hey @eleanorjboyd, this issue might need further attention.

@jjhelperin, you can help us out by closing this issue if the problem no longer exists, or adding more information.