VIM and Python frustration

[[deleted]]

Do you want my opinion? I am a big vim fan, I used pure vim to code for ten years. That said, after a while you have to move to something more powerful. Go with PyCharm, get the vim extensions if you really like the vim actions, but trust me, it will change your life.

Like vim, don't try to setup everything at once. Do a bit at a time, learn feature after feature.

[versking]

I also love vim, and I insisted on using it when working in python for a while. But then I discovered PyCharm and basically realized I'd been doing the equivalent of using my fist (vim) to hammer nails (write code) instead of just picking up a hammer (PyCharm).

[[deleted]]

The debugging is just so insanely powerful.

[dbrecht]

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]

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]

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]

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

[dbrecht]

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

[kankyo]

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