Python SystemExit — What It Means & How to Fix It

What Does This Error Mean?

SystemExit is raised when your program calls sys.exit(). It is not a bug — it is Python's way of cleanly stopping a program. But if it shows up unexpectedly, it means something in your code (or a library you are using) called sys.exit() when you did not expect it to.

Affected Models

Python 2.x
Python 3.x
All Python versions

Common Causes

Your code explicitly calls sys.exit() or os._exit() somewhere
A library or framework you are using calls sys.exit() on error — for example, argparse does this when command-line arguments are wrong
You caught a broad except Exception: block that accidentally caught SystemExit and then re-raised it
A test or script called sys.exit() and you were not expecting the whole process to stop
Code inside a finally block calls sys.exit(), overriding an earlier exit

How to Fix It

Search your code for any calls to sys.exit() or os._exit() and check whether they are being reached unexpectedly.

In most editors you can use Ctrl+F or Find in Files to search for 'sys.exit' across your whole project.
If you are using argparse and the error happens when parsing command-line arguments, argparse calls sys.exit(2) when arguments are invalid. Check your argument definitions and the values being passed.

You can catch this with: except SystemExit as e: — but usually it is better to fix the argument definitions instead.
If you need to catch all exceptions but still allow the program to exit cleanly, use 'except Exception' (which does NOT catch SystemExit) instead of 'except BaseException' (which DOES catch it).

SystemExit inherits from BaseException, not Exception — so a plain 'except Exception' block will not accidentally swallow it.
If a third-party library is calling sys.exit() and you need to prevent that, wrap the call in a try block and catch SystemExit specifically.

Example: try: library_function() except SystemExit: print('Library tried to exit — handled it.')
If you want to exit your program intentionally, sys.exit(0) means success and sys.exit(1) means failure. The number is the exit code that the operating system receives.

Using the right exit code matters if other scripts or systems check whether your program succeeded or failed.

When to Call a Professional

SystemExit is almost always something you can handle yourself. Check your own code for sys.exit() calls and search any libraries you use. If you need to prevent a library from exiting your program, catch SystemExit specifically and handle it.

Frequently Asked Questions

Is SystemExit actually an error?

Not really — it is a special exception that Python uses to stop the program cleanly. It inherits from BaseException, not Exception, which means it is in a special category. You only need to worry about it if your program is stopping when you did not expect it to.

Why does my try/except block not catch SystemExit?

Because SystemExit does not inherit from Exception — it inherits from BaseException. A plain 'except Exception' block will not catch it. To catch it, you need to write 'except SystemExit' or 'except BaseException' explicitly.

What is the difference between sys.exit() and os._exit()?

sys.exit() raises SystemExit and lets Python run cleanup code like finally blocks and context managers. os._exit() immediately stops the process — no cleanup, no finally blocks, nothing. Almost always use sys.exit() unless you have a specific reason to bypass cleanup.