![DataScience - Using ipdb.set_trace() in python interactive mode · Issue #533 · microsoft/vscode-jupyter · GitHub DataScience - Using ipdb.set_trace() in python interactive mode · Issue #533 · microsoft/vscode-jupyter · GitHub](https://user-images.githubusercontent.com/15957925/95265898-6ae96600-0832-11eb-9b99-584b60a5ffe4.png)
DataScience - Using ipdb.set_trace() in python interactive mode · Issue #533 · microsoft/vscode-jupyter · GitHub
![Cracking the Code — A Guide to Python Debugging Tools | by Patrick Kalkman | Python in Plain English Cracking the Code — A Guide to Python Debugging Tools | by Patrick Kalkman | Python in Plain English](https://miro.medium.com/v2/resize:fit:1400/1*V36zUGw4TzB-FWox8KAuzQ.png)
Cracking the Code — A Guide to Python Debugging Tools | by Patrick Kalkman | Python in Plain English
![python - Why does import pdb; pdb.set_trace trigger two different debugging scenarios when called differently in Spyder? - Stack Overflow python - Why does import pdb; pdb.set_trace trigger two different debugging scenarios when called differently in Spyder? - Stack Overflow](https://i.stack.imgur.com/Ratz6.png)
python - Why does import pdb; pdb.set_trace trigger two different debugging scenarios when called differently in Spyder? - Stack Overflow
![python - Why does import pdb; pdb.set_trace trigger two different debugging scenarios when called differently in Spyder? - Stack Overflow python - Why does import pdb; pdb.set_trace trigger two different debugging scenarios when called differently in Spyder? - Stack Overflow](https://i.stack.imgur.com/auOhI.png)
python - Why does import pdb; pdb.set_trace trigger two different debugging scenarios when called differently in Spyder? - Stack Overflow
![pdbe — a feature for internal Python debugger. Work with debugging in the Git style | by Dmytro Striletskyi | Medium pdbe — a feature for internal Python debugger. Work with debugging in the Git style | by Dmytro Striletskyi | Medium](https://miro.medium.com/v2/resize:fit:337/1*so2lUARPKHOtXXKuS30_2Q.png)