Exception hierarchy in Python - Time & Space Complexity

Time Complexity: Exception hierarchy

O(n)

Understanding Time Complexity

When working with exceptions, it's important to understand how catching errors affects program flow.

We want to see how the time to handle exceptions grows as the number of exception types increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

def handle_error(e):
    if isinstance(e, ValueError):
        print("Value error handled")
    elif isinstance(e, TypeError):
        print("Type error handled")
    elif isinstance(e, KeyError):
        print("Key error handled")
    else:
        print("Unknown error")

This code checks the type of an error and handles it accordingly by testing each exception type in order.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking the error type with multiple isinstance calls.
• How many times: Once for each exception type in the chain until a match is found or all are checked.

How Execution Grows With Input

As the number of exception types to check grows, the number of type checks grows too.

Input Size (number of exception types)	Approx. Operations (type checks)
3	Up to 3 checks
10	Up to 10 checks
100	Up to 100 checks

Pattern observation: The number of checks grows directly with the number of exception types to test.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle an exception grows linearly with the number of exception types checked.

Common Mistake

[X] Wrong: "Checking exceptions is always constant time because exceptions are rare."

[OK] Correct: Even if exceptions are rare, when they happen, the program may check many exception types one by one, so the time depends on how many types are checked.

Interview Connect

Understanding how exception handling scales helps you write clearer and more efficient error management in real projects.

Self-Check

What if we used a dictionary to map exception types to handlers instead of multiple if-elif checks? How would the time complexity change?

Practice

1. Which of the following is the base class for all built-in exceptions in Python?

easy

A. Exception

B. BaseException

C. Error

D. RuntimeError

Solution

1. Step 1: Understand Python's exception hierarchy

   All exceptions in Python inherit from BaseException, which is the root of the hierarchy.

2. Step 2: Identify the base class

   Exception inherits from BaseException, but BaseException is the top-level base class.

3. Final Answer:

   BaseException -> Option B

4. Quick Check:

   BaseException is the root of all exceptions [OK]

Hint: Remember: BaseException is the root of all exceptions [OK]

Common Mistakes:

• Confusing Exception with BaseException
• Thinking Error is a built-in base class
• Choosing RuntimeError as base

2. Which of the following is the correct syntax to catch all exceptions except system-exiting ones?

easy

A. except SystemExit:

B. except BaseException:

C. except Exception:

D. except RuntimeError:

Solution

1. Step 1: Recall exception hierarchy for catching exceptions

   Catching Exception catches most errors but excludes system-exiting exceptions like SystemExit and KeyboardInterrupt.

2. Step 2: Identify correct syntax

   except Exception: is the standard way to catch all regular exceptions safely.

3. Final Answer:

   except Exception: -> Option C

4. Quick Check:

   Use Exception to catch all but system-exiting exceptions [OK]

Hint: Use except Exception to avoid catching system-exit errors [OK]

Common Mistakes:

• Using except BaseException catches system exit too
• Catching only RuntimeError misses many exceptions
• Using except SystemExit catches only exit exceptions

3. What will be the output of this code?

try:
    x = 1 / 0
except ArithmeticError:
    print('ArithmeticError caught')
except ZeroDivisionError:
    print('ZeroDivisionError caught')

medium

A. ArithmeticError caught

B. ZeroDivisionError caught

C. No output, program crashes

D. SyntaxError

Solution

1. Step 1: Understand exception hierarchy for ZeroDivisionError

   ZeroDivisionError is a subclass of ArithmeticError.

2. Step 2: Check which except block matches first

   Since ArithmeticError comes before ZeroDivisionError, the first except block catches the exception.

3. Final Answer:

   ArithmeticError caught -> Option A

4. Quick Check:

   Parent exception catches before child [OK]

Hint: Parent exceptions catch before child exceptions in order [OK]

Common Mistakes:

• Expecting ZeroDivisionError block to run first
• Thinking exception order does not matter
• Assuming program crashes without handling

4. Find the error in this code snippet:

try:
    open('file.txt')
except IOError:
    print('File error')
except FileNotFoundError:
    print('File not found')

medium

A. open() needs a mode argument

B. IOError should be replaced with Exception

C. No error, code is correct

D. FileNotFoundError should come before IOError

Solution

1. Step 1: Understand exception hierarchy between IOError and FileNotFoundError

   FileNotFoundError is a subclass of IOError.

2. Step 2: Check order of except blocks

   The more specific exception (FileNotFoundError) must come before the more general (IOError) to avoid unreachable code.

3. Final Answer:

   FileNotFoundError should come before IOError -> Option D

4. Quick Check:

   Specific exceptions must precede general ones [OK]

Hint: Place child exceptions before parent exceptions in except blocks [OK]

Common Mistakes:

• Putting general exceptions before specific ones
• Assuming IOError and FileNotFoundError are unrelated
• Thinking open() requires mode argument always

5. You want to catch all exceptions except KeyboardInterrupt and SystemExit. Which is the best way to write the except block?

hard

A. except Exception:

B. except BaseException:

C. except (KeyboardInterrupt, SystemExit):

D. except (Exception, KeyboardInterrupt, SystemExit):

Solution

1. Step 1: Recall exception hierarchy for KeyboardInterrupt and SystemExit

   Both KeyboardInterrupt and SystemExit inherit directly from BaseException, not Exception.

2. Step 2: Choose except block that excludes these exceptions

   except Exception: catches all exceptions except KeyboardInterrupt and SystemExit, which is the desired behavior.

3. Final Answer:

   except Exception: -> Option A

4. Quick Check:

   Exception excludes system-exiting exceptions [OK]

Hint: Use except Exception to exclude system-exiting exceptions [OK]

Common Mistakes:

• Using except BaseException catches everything including system exit
• Catching KeyboardInterrupt and SystemExit explicitly when not needed
• Combining Exception with KeyboardInterrupt in except tuple