Generic exception handling in Python - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is generic exception handling in Python?

Generic exception handling means catching any kind of error that might happen during program execution using a broad exception clause like except Exception:. It helps prevent the program from crashing unexpectedly.

beginner

How do you write a generic exception handler in Python?

You use a try-except block with except Exception: to catch all exceptions that inherit from the base Exception class. For example:

try:
    # code
except Exception:
    # handle error

intermediate

Why should you be careful when using generic exception handling?

Because it catches all exceptions, it can hide bugs or important errors. It might make debugging harder if you don't log or handle errors properly. It's best to use it when you want to catch unexpected errors but still know what happened.

intermediate

What is the difference between except: and except Exception:?

except: catches all exceptions including system-exiting ones like KeyboardInterrupt and SystemExit. except Exception: catches most errors but lets system-exiting exceptions pass through, which is usually safer.

beginner

Show a simple example of generic exception handling that prints the error message.

try:
    x = 1 / 0
except Exception as e:
    print(f"An error occurred: {e}")

This code catches any error and prints what went wrong.

Which keyword is used to catch all exceptions in Python safely?

A catch all:

B except BaseException:

C except Exception:

D except:

except Exception: catches most errors but excludes system-exiting exceptions, making it safer than a bare except:.

What happens if you use a bare except: clause?

A It only catches syntax errors.

B It catches all exceptions including system exit signals.

C It catches no exceptions.

D It only catches user-defined exceptions.

A bare except: catches every exception, including KeyboardInterrupt and SystemExit, which can stop the program unexpectedly.

Why might generic exception handling make debugging harder?

A Because it hides all errors if not logged or re-raised.

B Because it only catches syntax errors.

C Because it stops the program immediately.

D Because it only works with specific exceptions.

Generic handlers catch all errors, so if you don't log or handle them properly, you might not know what went wrong.

Which of these is a good practice when using generic exception handling?

A Log the error message inside the except block.

B Ignore the error silently.

C Use it everywhere without specific exceptions.

D Never use try-except blocks.

Logging errors helps you understand what happened and fix bugs later.

What does this code do?

try:
    print(10 / 0)
except Exception as e:
    print(f"Error: {e}")

A Does nothing.

B Crashes the program.

C Prints 0.

D Prints 'Error: division by zero'.

The division by zero raises an exception caught by the generic handler, which prints the error message.

Explain what generic exception handling is and when you might use it.

Think about catching many errors at once to keep the program running.

Describe the difference between a bare except and except Exception in Python.

Consider what kinds of exceptions each catches and why that matters.

Practice

1. What does generic exception handling with except Exception do in Python?

easy

A. It automatically fixes errors without any code changes.

B. It only catches syntax errors in the code.

C. It catches most types of errors to prevent the program from crashing.

D. It ignores all errors and continues running silently.

Solution

1. Step 1: Understand the role of except Exception

   This clause catches exceptions that are instances of the Exception class or its subclasses, which covers most runtime errors.

2. Step 2: Recognize its effect on program flow

   By catching these exceptions, the program avoids crashing and can handle errors gracefully.

3. Final Answer:

   It catches most types of errors to prevent the program from crashing. -> Option C

4. Quick Check:

   Generic exception handling = catches most errors [OK]

Hint: Generic catch uses except Exception to stop crashes [OK]

Common Mistakes:

• Thinking it only catches syntax errors
• Believing it fixes errors automatically
• Assuming it ignores errors silently

2. Which of the following is the correct syntax to catch all exceptions in Python?

easy

A. try:
pass
except:

B. try:
pass
except Error:

C. try:
pass
catch Exception:

D. try:
pass
except Exception:

Solution

1. Step 1: Identify correct exception syntax

   In Python, to catch most exceptions, use except Exception:. The bare except: also catches exceptions but is less specific.

2. Step 2: Check syntax correctness

   try: pass except Exception: uses the correct keyword except with the Exception class, which is the recommended way.

3. Final Answer:

   try:\n pass\nexcept Exception: -> Option D

4. Quick Check:

   Correct generic catch syntax = except Exception: [OK]

Hint: Use except Exception: to catch most errors correctly [OK]

Common Mistakes:

• Using catch instead of except
• Using undefined Error class
• Using bare except without colon

3. What will be the output of this code?

try:
    x = 5 / 0
except Exception:
    print("Error caught")
print("Done")

medium

A. ZeroDivisionError\nDone

B. Error caught\nDone

C. Done

D. No output, program crashes

Solution

1. Step 1: Identify the error raised

   The code tries to divide 5 by 0, which raises a ZeroDivisionError, a subclass of Exception.

2. Step 2: Check exception handling and output

   The except Exception block catches this error and prints "Error caught". Then the program continues and prints "Done".

3. Final Answer:

   Error caught\nDone -> Option B

4. Quick Check:

   ZeroDivisionError caught = prints error message and continues [OK]

Hint: Generic except catches ZeroDivisionError and prints message [OK]

Common Mistakes:

• Expecting program to crash with error message
• Thinking error message is printed automatically
• Missing that 'Done' prints after exception

4. Find the error in this code snippet:

try:
    print(10 / 0)
except Exception
    print("Caught error")

medium

A. Missing colon after except Exception

B. Division by zero is not caught by Exception

C. print statement syntax is wrong

D. try block should have an else clause

Solution

1. Step 1: Check syntax of except block

   The except line is missing a colon at the end, which is required in Python syntax.

2. Step 2: Confirm other parts are correct

   Division by zero raises ZeroDivisionError, subclass of Exception, so it is caught. The print statement syntax is correct. Else clause is optional.

3. Final Answer:

   Missing colon after except Exception -> Option A

4. Quick Check:

   except line must end with colon : [OK]

Hint: Always put colon after except Exception: [OK]

Common Mistakes:

• Forgetting colon after except
• Thinking division by zero is uncaught
• Believing else clause is mandatory

5. You want to catch any error in a function but also print the error message. Which code correctly does this?

def safe_divide(a, b):
    try:
        return a / b
    except Exception as e:
        print(e)
        return None

hard

A. This code catches all exceptions and prints the error message.

B. This code only catches ZeroDivisionError and ignores others.

C. This code will crash if b is zero because it lacks exception handling.

D. This code catches exceptions but does not print any message.

Solution

1. Step 1: Analyze the try-except block

   The function tries to divide a by b. If any exception occurs, it is caught by except Exception as e.

2. Step 2: Check error message printing and return

   The caught exception is printed using print(e), then the function returns None to indicate failure.

3. Final Answer:

   This code catches all exceptions and prints the error message. -> Option A

4. Quick Check:

   except Exception as e prints error message [OK]

Hint: Use except Exception as e to print error details [OK]

Common Mistakes:

• Not using 'as e' to access error message
• Assuming only ZeroDivisionError is caught
• Missing return after exception