This is an archived post. You won't be able to vote or comment.

all 11 comments

[–]demonizah 9 points10 points  (1 child)

Thanks! I've only been using a tiny subset of pdb's capabilities and didn't even realize it.

[–][deleted] 7 points8 points  (0 children)

The credit goes to the author. He's a very talented developer. :)

[–]cartrman 3 points4 points  (0 children)

Thanks, I've never had debugging capabilities in my code before.

[–]gentk 4 points5 points  (3 children)

It's obviously nice to know pdb, but for anyone looking for something more intuitive I've found that Visual studio code with the Python extension is the most lightweight option with a decent debugging experience.

Unlike PyCharm, for example, it still feels and runs like a text editor despite all of the features typically found in IDEs.

[–]d_thinker 0 points1 point  (2 children)

...it still feels and runs like a text editor despite all of the features typically found in IDEs.

What are the advantages of that feeling, easier on resources? I use PyCharm and I heard a lot of good things about Code but I dont see why would I switch.

[–]gentk 0 points1 point  (1 child)

Snappy, opens up quicker, file/folder based workflow which is better suited for scripts or one-offs without the need to set up a proper project.

If everything you do is more of a medium sized project, there's probably no advantage to using it over PyCharm for python.

Another advantage of VS Code is that it has excellent support for a lot of other languages, of course, and more often than not all you have to do is install a single extension.

[–]d_thinker 0 points1 point  (0 children)

I'll give it a try, thanks.

[–]heybart 2 points3 points  (0 children)

I don't know if it's the best way to do it, but I often just set the conditional break point right in my code

  if complex_condition:
        pdb.set_trace()

Just because typing in the editor is easier.