How to debug Python code in Visual Studio Code

qodo.ai

12 pointsfour_fifths4 comments

This hits me in the feels right now. I've been trying to convert from JetBrains to VS Code. And every time I do, stuff like this gets in my way.

For instance: Python. Pycharm: I click on the side for a breakpoint, and then trigger a test to run, and it just works. I keep thinking I'm missing something for VS Code as it never quite works as smooth, but I have better things to do and I move on.

And then I see an article like this which makes it seem like it's not so straightforward.

I recently had to switch from Jetbrains to VSCode for Go development and it took days of troubleshooting to get the debugger working. I don't even remember what the problem ended up being offhand.

And that's in addition to having to acclimate myself to completely different and objectively worse syntax highlighting (you can customize the colors of more types of tokens using Jetbrains syntax highlighting system), worse global find+replace, and losing all Intellisense features (hovering on types, ctrl+click to type definitions, etc.) whenever there is a syntax error anywhere in the entire repo.

I write in Go in IntelliJ full-time, do I miss any features from VSCode? Why did you move?

Nope. We were forced to by management.

Reply on news.ycombinator.com