[Feature Request] Add options for handling errors encountered during debugging

[tzengshinfu]

Hello,

While debugging, I encountered an "undefined variable" error.
However, my attention was focused on the editor area, and the spelling error notification happened to be obscured by the line highlight where my cursor was.
As a result, I didn't notice that Pylance had already reported the error.

Would it be possible for the Python debugger to check for Pylance-detected errors before starting a debug session,
and instead jump directly to the PROBLEMS panel instead of launching the debugger?
Just like how VSCode behaves with JavaScript.

Although this may only save a few seconds, it can significantly reduce wasted attention and improve productivity, especially for beginners who go through a lot of trial and error.

Thank you very much for your help!

VSCode version: 1.100.2
Python Debugger version: 2025.9.2025052001
Pylance version: 2025.5.1

[tzengshinfu]

By combining multiple VSCode extension APIs,
I have been able to implement a proof of concept for the aforementioned functionality in my own extension without relying on a specific extension (such as Pylance).

Next, I will submit a pull request to the official extension repository.

[eleanorjboyd]

Thanks for the idea- will need to investigate more

[eleanorjboyd]

Has anything like this been considered or investigated? @karthiknadig