Why is "except:" able to catch this error but not "except Exception, e:"?

Question

I have the following file:

from fabric.api import env, execute, run

env.hosts = ['1.2.3.4']

def taskA():
    run('ls')

def main():
  try:
    execute(taskA)
  except:
    print "Exception Caught"

main()

I am able to see "Exception Caught" printed when I run this:

$ python test.py
[1.2.3.4] Executing task 'taskA'
[1.2.3.4] run: ls

Fatal error: Timed out trying to connect to 1.2.3.4 (tried 1 time)

Underlying exception:
    timed out

Aborting.
Exception Caught

However, when I switch it to this:

def main():
  try:
    execute(taskA)
  except Exception, e:
    print "Exception Caught", e

main()

I don't see the exception being caught:

[1.2.3.4] run: ls

Fatal error: Timed out trying to connect to 1.2.3.4 (tried 1 time)

Underlying exception:
    timed out

Aborting.

Is there a reason why I am able to catch the error in the code above and not below?

I don't see a traceback, so the exception *was* caught. Are you sure you are printing correctly? Also, use `except Exception as e:`. — Martijn Pieters, Jul 31 '17 at 20:02
@MartijnPieters: No traceback probably means it's a SystemExit. — user2357112, Jul 31 '17 at 20:04

user2357112 · Accepted Answer · 2017-07-31T20:15:14.077

This exception does not derive from Exception. It looks like a SystemExit, which derives from BaseException directly. except Exception only catches instances of Exception.

If you really want to catch absolutely all exceptions, you can do that with

except BaseException as e:

SystemExit is thrown by sys.exit and a few similar functions to cause an interpreter shutdown (or at least end the thread) while still running __exit__ methods and finally blocks. It can also be thrown manually.

BaseException exists so SystemExit and a few similar exceptions aren't caught by except Exception blocks that usually aren't intended to handle them. It's similar to Java's Throwable. Personally, I wish plain except: blocks didn't catch BaseException; it defeats some of the purpose of having BaseException in the first place.

TheoretiCAL · Answer 2 · 2017-07-31T20:16:18.193

When you use except Exception, e, it

doesn't catch BaseException or the system-exiting exceptions SystemExit, KeyboardInterrupt and GeneratorExit

where as except catches all exception types. See Difference between except: and except Exception as e: in Python.

As a result you see "Exception Caught" when using except, however not when using except Exception, e

From the fab docs

If a Python exception is thrown, fab aborts with an exit status of 1.

Why is "except:" able to catch this error but not "except Exception, e:"?

2 Answers2