Blacklist modules when stepping through source code

[Julian]

Hi! (Love pudb, been using it for a long time now).

This is a feature request that just came up for a way to blacklist modules when nexting. The reason being that t is great when you're not switching stack frames, or switching but then switching back immediately, but for other times, say, when debugging an application running in an event loop or using big chunks of a large library where you want to skip the module running the event loop or the third-party code, it'd be nice to have a way to blacklist.

If you don't have time for this, consider it a reminder for myself, I'll try to get to it at some point if I beat you to it.

Thanks.

[inducer]

That's a good idea, and I'd be happy to see any work you do towards that goal. I'm wondering what UI could work here. The best I could come up with is a multi-line text box entry that lets you enter the blacklisted modules as one-per-line, with shell globbing allowed.

[Julian]

Sounds good to me. I'll take a look at what I can cook up. Cheers.

[mnieber]

I have a use-case where this feature would be very convenient. As a reference, one can look at the "Ignore " feature of the Chrome debugger. This allows you to ignore one or more files (with a glob pattern), which means that - when stepping in - it runs through the lines in the ignored files until a file is reached that is not ignored, and then breaks there.

[nikhilweee]

Just came to say that this feature would be really helpful. I frequently debug code which involves large libraries (e.g. pytorch) and it would be really convenient to skip over a few specified files which hold wrapper scripts.