Visual Studio Code Python debugging "Exception has occurred SystemExit"

Question

I've been using Visual Studio code for a long time with the Python extension.

Currently I have Visual Studio Code version 1.27.2, Python extension "ms-python.python" version 2018.8.0, python version 3.6.6, hosted by a Windows 10 1803 Enterprise Edition system.

Compared to the past, the latest version of Code / MS Python behaves differently in the debugging process.

In the past the execution of the following Python code, within Visual Studio Code, would not have generated any exceptions:

# Import exit from sys
from sys import exit as sys_exit
# Exit to system with errorlevel set to 1
sys_exit(1)
# Next instruction is never executed.
# Executing the script directly from the terminal in Windows sets the
# errorlevel to 1 and the script execution is terminated. 
print('unreachable code')

Now the result is a SystemExit exception when sys_exit(1) instruction is executed (VSCode screenshot).

Question: is there a way to disable this behavior and return to the previous one?

I looked at the VS Code source and this should be pretty easy for them to implement. They have this feature built into Visual Studio Code that you can configure the debugger to ignore specific exceptions types. — Timothy C. Quinn
– Timothy C. Quinn, Commented Feb 29, 2020 at 17:37
I have raised a feature request with the VS Code project here: github.com/microsoft/vscode/issues/91822 . Please give it a look. — Timothy C. Quinn
– Timothy C. Quinn, Commented Feb 29, 2020 at 18:05
Note: In theory, the 'unreachable code' print statement should not be reachable as by definition, sys.exit() should be a hard exit for the code and no further lines should run. — Timothy C. Quinn
– Timothy C. Quinn, Commented Feb 29, 2020 at 18:07
This is the real issue. Please upvote. It is still open: github.com/microsoft/vscode-python/issues/850 — T3rm1
– T3rm1, Commented Apr 15, 2020 at 13:16

Josh Rodstein · Accepted Answer · 2018-11-02 21:21:45Z

39

I ran into something similar while debugging my flask application. My work-around was to uncheck "Uncaught Exceptions" in the breakpoint menu at the bottom of the debug window.

edited Nov 2, 2018 at 21:21

answered Oct 31, 2018 at 15:43

Josh Rodstein

5313 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

10 Comments

kishkin Over a year ago

It might be a workaround for some, but there is a problem if you are going to debug some tests: unchecking "Uncaught Exceptions" results in no tests ran. This behavior is considered a bug, so will be fixed: github.com/Microsoft/ptvsd/issues/982#issuecomment-435584288

Mass Dot Net Over a year ago

Still hasn't been fixed as of May 2020.

Scott Fraley Over a year ago

sys.exit() is how you exit a Python script, is it not!? Can't understand why the heck it would be an exception. :(

qJake Over a year ago

2021 here, still not fixed. sys.exit(1) produces: Exception has occurred: SystemExit

MiniMe Over a year ago

2022 here, still not fixed

|

10 Rep · Accepted Answer · 2020-10-15 02:38:51Z

5

sys.exit can have a parameter. If you don't give it one it returns None. If anything besides 0 is returned its considered an error exit. So using this works

sys.exit(0)

edited Oct 15, 2020 at 2:38

10 Rep

2,2687 gold badges21 silver badges34 bronze badges

answered Oct 15, 2020 at 2:16

Gman

671 silver badge1 bronze badge

2 Comments

sny Over a year ago

Console applications returning non 0 exit code is not an Exception or necessarily an error.

Matt S Over a year ago

Changing the behavior of an application to work around an IDE limitation is not a good solution.

Collectives™ on Stack Overflow

Visual Studio Code Python debugging "Exception has occurred SystemExit"

2 Answers 2

10 Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

10 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related