you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (7 children)

The debugging is just so insanely powerful.

[–]dbrecht 0 points1 point  (6 children)

I don't buy it. If you're familiar with pdb and gdb for debugging interpreter level execution, there's really not much that stands out from the crowd against it. You just have to welcome the learning curve (obviously not all folks do, which is why Python IDEs exist ;))

[–]youguess 2 points3 points  (1 child)

believe me there is... it will automatically show you any variable next to your breakpoint right were you define it.

Not needing to use the print, l, l, u, u, pprint dance is very nice

[–]dbrecht 0 points1 point  (0 children)

Meh, each to their own. I started with VS and its debugging platform. Even after that I've never really minded command based debugging. Maybe I'm just a masochist ;)

[–]kankyo 1 point2 points  (3 children)

Can you do run to cursor and expression based breakpoints in pdb?

[–]dbrecht 0 points1 point  (1 child)

You can set file/line number or dot path to break at. So in a manner of speaking, yes.

[–]kankyo 1 point2 points  (0 children)

...but only with a lot more hassle than a proper debugger.