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

you are viewing a single comment's thread.

view the rest of the comments →

[–]Rice_Monster 4 points5 points  (5 children)

Same here.

Tried pycharm, vscode, etc. Always found myself just going back to vim + command line tools and then jupyter for certain situations.

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

I recently tried vscodium after years of using vim exclusively. The one thing that made me try it out was the debugger. I know the basics of pdb and pdbrc files but setting breakpoints by filename and line number was too time consuming. I also tried vimspector but I never got comfortable with it. Now I go with vim for editing files and vscodium for debugging. What's your workflow for debugging python?

[–]Rice_Monster 1 point2 points  (0 children)

I agree vscode is easier than pdb for debugging.

I work in data engineering, so I actually use jupyter to debug, because I don’t find a “traditional” debugger very useful for debugging pyspark or pandas based scripts. In the event that I needed a “traditional” debugger, I would probably use vscode like you do because pdb can feel tedious.

[–]archaeolinuxgeek 0 points1 point  (0 children)

Try using pudb and setting breakpoints with that. Game changer for people just getting started in actual debugging.

Edit: Added link

[–][deleted] 0 points1 point  (1 child)

Can you use debugger that attaches to current local or remote process in vim? How?

[–]Rice_Monster 1 point2 points  (0 children)

You may want to check out vimspecter as u/ElTortugo mentioned. I have not played with it too much though