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
[severity:It's more difficult to complete my work] [regression] [worked-in:vs2019]
In VS2022, I'm unable to disable any python exceptions.
If a debugger is attached, it will break on every single exception even the benign ones. Which makes debugging impossible with certain scripts that use exceptions part of non-erroneous executions.
I tried disabling/enabling all in the exceptions window. No impact either way.
I tried different python versions. no impact.
I tried unchecking the "new exception helper". I get a different exception window (btw, much more helpful than the "new" one), but the "break when ..." is greyed out. So I can't disable an exception from there either.
I played with other options, no luck.
Vs2019 had a similar issue, but if i remember correctly, it had a "use legacy debugger" option, which I think ended up resolving this issue. Unfortunately, you removed that option.
Original Comments
Feedback Bot on 10/12/2023, 04:02 AM:
(private comment, text removed)
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered:
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work] [regression] [worked-in:vs2019]
In VS2022, I'm unable to disable any python exceptions.
If a debugger is attached, it will break on every single exception even the benign ones. Which makes debugging impossible with certain scripts that use exceptions part of non-erroneous executions.
I tried disabling/enabling all in the exceptions window. No impact either way.
I tried different python versions. no impact.
I tried unchecking the "new exception helper". I get a different exception window (btw, much more helpful than the "new" one), but the "break when ..." is greyed out. So I can't disable an exception from there either.
I played with other options, no luck.
Vs2019 had a similar issue, but if i remember correctly, it had a "use legacy debugger" option, which I think ended up resolving this issue. Unfortunately, you removed that option.
Original Comments
Feedback Bot on 10/12/2023, 04:02 AM:
(private comment, text removed)
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: