Step into non-user code

[jtpio]

It is possible to step into a local module just fine (#248). But stepping into non-user code such as the standard library or third-party libraries will give something like the following:

Note that the behavior is similar in VS Code when justMyCode is set to true in the launch configuration:

After some investigation, it seems that justMyCode is passed at launch. Also this parameter is not part of the DAP.

We should check whether we can make use of this parameter with the interactive mode.

[dbalabka]

It pretty often cases when you are required to investigate vendor library sources during a debugging session. For me, it is the most frequent use case.

[JohanMabille]

Notice that in the context of Jupyter, there is no Launch request since the interpreter is always running.

[jnarula5]

Hi Jeremy,

Can you please point me to the code where justMyCode needs to be set to False?

Thanks,
Jaspreet

[jtpio]

Last time we investigated this, justMyCode was not part of the DAP and it seemed like it would require a couple of changes in xeus-python and / or the debugger extension.

[hsinhungli]

I just started trying to use the Jupyter debugger, and run into the same issue. I feel that this is the most needed function in my application. That is, stepping into the functions that are loaded from existed modules or library stored in other folders on my computer. I wonder whether this is issue has been resolved. Based on the previous message, there is still no work around (e.g., justMyCode) for this? Is that correct?

[JohanMabille]

If I remember correctly, passing this paramete was required to get PTVSD break into user code (but that is pure cargo-culting, I did nt investigate more). I can test again now that the debugger has migrated to debugpy.

[jtpio]

Closing in favor of jupyterlab/jupyterlab#11566 and ipython/ipykernel#811

[echarles]

Thx @jtpio for the backlink. This discussion is interesting.