Why Exception hierarchy in Python? - Purpose & Use Cases

The Big Idea

What if you could catch many errors with just one simple rule instead of dozens of checks?

The Scenario

Imagine you are writing a program that reads files, connects to the internet, and processes data. You try to catch errors one by one, writing separate code for each possible problem like file not found, connection lost, or wrong data format.

The Problem

This manual way is slow and confusing. You might miss some errors or write repetitive code. When new errors happen, you have to add more checks everywhere, making your program messy and hard to fix.

The Solution

Using an exception hierarchy groups related errors under common categories. You can catch broad groups of errors or specific ones easily. This keeps your code clean, organized, and ready for new error types without rewriting everything.

Before vs After

✗ Before

try:
    open('file.txt')
except FileNotFoundError:
    print('File missing')
except ConnectionError:
    print('No internet')

✓ After

try:
    open('file.txt')
except OSError:
    print('File or connection problem')

What It Enables

It enables writing simpler, clearer error handling that adapts easily as your program grows.

Real Life Example

Think of a customer service center where calls are first sorted by department (billing, tech support) before being handled by specialists. Exception hierarchy sorts errors similarly, so your program knows where to look first.

Key Takeaways

Manual error handling is repetitive and fragile.

Exception hierarchy groups related errors for easier handling.

This leads to cleaner, more maintainable code.

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