You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Option to enable breakpoints to stop when warnings are raised in the python debugger #17200
Originally posted by whentheworldfallsapart May 18, 2021
It would be nice if under the breakpoints drop down in the debugger if there was an option to set a breakpoints for warnings (understanding that warnings are handled completely different from exceptions in python). Numpy allows raising warnings as errors "np.seterr(all='raise')", this can be used to help locate what is causing a divide by zero warning for example. But most packages dont have this feature, and tracing down warning while looping over large sets of data can often require print statements to locate which input data is causing a warning inside a package. Having the feature in vscode debugging to add breakpoints to stop on warnings would be very helpful. (This a popular feature in MATLAB for example, allowing the user to stop on warnings).
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 5 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.
Thank you for submitting your feature request and everyone who considered it! Unfortunately this issue did not receive enough votes over the allotted time, and so we are closing the issue.
Activity
brettcannon commentedon Sep 1, 2021
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 5 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.
brettcannon commentedon Nov 1, 2021
Thank you for submitting your feature request and everyone who considered it! Unfortunately this issue did not receive enough votes over the allotted time, and so we are closing the issue.