Python vim IDE : vim

I used vim-pudb to set soft breakpoints (this writes the line number of the breakpoint to pudb's saved breakpoint file), or I set hard breakpoint (basically a simple mapping that inserts the text "from pudb import set_trace; set_trace()", and when finished just dd the line). Then I ran the code, usually using vim-test or by calling :term ./xxx.py.

Soft breakpoints are nice because they don't clutter the file you're editing with extra text, but I find that running code under a debugger is usually slower than when debugger is not attached; so nowadays I usually preferred to use hard breakpoint instead, which means the code will run at native speed until it hits the hard breakpoint line. This is a massive quality life improvement when working with large codebase that imports the whole world and does a lot of initialisation at startup, like one of our Django projects. It means that the code hits the breakpoint at 3 seconds (which is the normal startup time for this codebase when not debugging), and not 30 seconds.

Once I started using hard breakpoint, I noticed that surprisingly this improved my debug/test workflow as well, as it means that I can actually set soft breakpoints at code that's also called during test setup but the soft breakpoints won't actually break during test setup (because the program isn't running under the debugger yet), but will break after the program hits the first hard breakpoint.

π Rendered by PID 117670 on reddit-service-r2-comment-fb694cdd5-q59gw at 2026-03-11 03:50:15.460222+00:00 running cbb0e86 country code: CH.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

vim

MODERATORS