![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
تويتر \ Jake VanderPlas على تويتر: "(note that #2 can be replaced with `breakpoint()` in newer versions of Python... but someone once said "explicit is better than implicit"...)"
![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
Will McGugan on Twitter: "This is cool, a #Python debugger using Rich for output. https://t.co/SYLSSPn6Yu https://t.co/jaNLvtXXyA" / Twitter
![Args are being ignored by pytest config: impossible to run ipdb even with -s · Issue #9124 · microsoft/vscode-python · GitHub Args are being ignored by pytest config: impossible to run ipdb even with -s · Issue #9124 · microsoft/vscode-python · GitHub](https://user-images.githubusercontent.com/636391/70852281-e511be00-1e9f-11ea-9b60-93d87e5655df.png)