While debugging interactiveshell.py wont let go! the debugging only happens inside interactiveshell.py

Bug: Notebook Editor, Interactive Window, Editor cells

Description

Basically, as you can see in the screencast below, whenever I try to debug a cell, I’ll face interactiveshell.py and instead the debugger wants me to debug this file and would not get out! no matter what I do! even if I keep pressing step-out, or if I press continue running until the next breakpoint, it just simply ends the debugging! Since this is along the line of my previous issue, microsoft/vscode-jupyter#1656 , I’m unsure if this is something typical and routine or not (to be honest I’m highly sckeptial if it is!)

Steps to cause the bug to occur

1. write some code in a cell
2. try to debug it!

Actual behavior

it stucks in the interactiveshell.py

Expected behavior

gets out of it and debug my code instead!

second screencast:

Your Jupyter and/or Python environment

Please provide as much info as you readily know

• Jupyter server running: Windows 10 WSL
• Extension version: 2020.1.58038 (13 January 2020)
• VS Code version: 1.41
• Setting python.jediEnabled: false
• Python and/or Anaconda version: 3.7.3 (Anaconda3-2019.03-Linux-x86_64)
• OS: Windows 10 WSL subsystem (distro): ubuntu 18.04
• Virtual environment: conda

Developer Tools Console Output

https://gofile.io/?c=KeRuTl

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer

[rchiodo]

In the gifs, you’re hitting step over. That prevents it from stepping ‘into’ your code. Try hitting step into instead. It should eventually do something like this:

You can see in the interactiveShell.py that it’s evaling and compiling the code of the cell that was sent. When it executes the code, that’s when you have to hit F11 (step into) instead of F10 (step over) if you want to step into your code.

If breakpoints were working (but they’re not), then you could just hit F5 to get to your breakpoints.

[Coderx7]

Thanks a lot, I checked that, and yes, steping in, does go into my code, However, I also noticed, now, when in interactiveshell.py, F5 and step over work as well! While previously they were’nt working at all! I’m not sure what has happenened but its back to its former behavior!