Raising Exceptions in Python0%

Raising Exceptions in Python

Intermediate8 min read•Updated: 2026-10-01

Raising Exceptions in Python

While Python automatically raises exceptions when illegal runtime operations occur (like dividing by zero or indexing out of bounds), professional Python developers also intentionally trigger exceptions using the raise statement. Raising exceptions allows functions to reject invalid parameters, signal invariant violations, and propagate contextual error messages up the execution call stack.

1. The `raise` Statement

The raise keyword stops normal sequential execution and signals an exception. You can raise any instance or subclass of BaseException (almost always a subclass of Exception).

1def set_user_age(age: int):
2    if not isinstance(age, int):
3        raise TypeError(f"Age must be an integer, received {type(age).__name__}.")
4    if age < 0 or age > 130:
5        raise ValueError(f"Age {age} is out of realistic physiological range (0-130).")
6    
7    print(f"User age recorded: {age}")
8 
9set_user_age(28)
10 
11try:
12    set_user_age(-5)
13except ValueError as err:
14    print(f"Validation failed: {err}")

2. Re-raising Exceptions (Propagating After Logging)

Sometimes an except block needs to log diagnostic information, clean up temporary data, or execute metrics tracking, but still allow the exception to propagate to caller functions.

A bare raise statement inside an except clause re-raises the active exception currently being handled:

1import logging
2 
3def execute_remote_query(query: str):
4    try:
5        # Simulate network failure
6        raise ConnectionResetError("Connection lost to database cluster.")
7    except ConnectionResetError as err:
8        # 1. Log the failure locally
9        print(f"[AUDIT LOG] Database operation failed: {err}")
10        
11        # 2. Re-raise the active exception without losing original traceback!
12        raise
13 
14try:
15    execute_remote_query("SELECT * FROM orders")
16except ConnectionResetError:
17    print("Caller caught re-raised connection error.")

3. Exception Chaining: `raise ... from ...`

When building modular software or library wrappers, you often want to transform a low-level implementation error into a meaningful domain-level exception while preserving the original diagnostic cause.

Python supports Exception Chaining using the from clause:

1class PaymentGatewayError(Exception):
  """Raised when a payment processor transaction fails."""
  pass
4 
5def charge_card(card_token: str, amount: float):
  try:
      # Low level network or crypto failure
      raise TimeoutError("Socket read timed out after 10000ms.")
  except TimeoutError as original_error:
      # Wrap the raw socket error inside a domain-specific PaymentGatewayError
      raise PaymentGatewayError("Payment could not be completed.") from original_error

When Python prints the traceback for this, it explicitly shows:

1The above exception was the direct cause of the following exception:
2PaymentGatewayError: Payment could not be completed.

The original error is preserved in the __cause__ attribute of the new exception.

4. Suppressing Context with `raise ... from None`

If the low-level exception exposes sensitive internal details (like database credentials, internal server IPs, or confusing library internals) that would confuse API consumers, suppress the chain using from None:

1def parse_security_pin(raw_pin: str) -> int:
  try:
      return int(raw_pin)
  except ValueError:
      # Hide the underlying ValueError traceback completely
      raise ValueError("PIN must consist of 4 to 6 numeric digits.") from None

Now, the traceback will only show ValueError: PIN must consist of 4 to 6 numeric digits. without the secondary "During handling of the above exception..." message.

5. Defensive Programming Best Practices

1
Always include informative error messages: Avoid raise ValueError(). Prefer raise ValueError(f"Expected positive price, got {price}").
2
Choose the most appropriate built-in exception:

Bad argument type: TypeError
Bad argument value/range: ValueError
Feature not ready: NotImplementedError
State violation: RuntimeError

1
Never raise strings: In modern Python, raise "Error" is a fatal TypeError. You must raise an Exception instance or class.

⚠️ Common Intermediate Mistakes & Gotchas

1. Raising String Literals

In modern Python, you must raise an instance or subclass of BaseException. Writing raise "Error" results in an immediate TypeError.

2. Losing Original Exception Tracebacks

When re-raising or transforming an exception, use raise NewException(...) from err to preserve the causal chain for easier debugging.

💻 Try It Yourself: Inventory Stock Guard

Scenario

Write a function dispense_item(inventory, item_name, count) that raises KeyError if the item is not in stock and ValueError if the requested count exceeds available stock.

Complete Solution

1def dispense_item(inventory: dict, item: str, count: int):
  if item not in inventory:
      raise KeyError(f"Item '{item}' is not tracked in inventory.")
  if count <= 0:
      raise ValueError("Requested count must be positive.")
  if count > inventory[item]:
      raise ValueError(f"Insufficient stock for '{item}'. Requested: {count}, Available: {inventory[item]}")
  
  inventory[item] -= count
  print(f"Dispensed {count}x '{item}'. Remaining: {inventory[item]}")
11 
12stock = {"Laptops": 5, "Mice": 20}
13try:
  dispense_item(stock, "Laptops", 3)
  dispense_item(stock, "Keyboards", 1)
16except (KeyError, ValueError) as err:
  print(f"Error caught: {err}")

Expected Output

1Dispensed 3x 'Laptops'. Remaining: 2
2Error caught: 'Item \'Keyboards\' is not tracked in inventory.'

Interactive Quiz• Knowledge Check

Practice Quiz

Question 1

Which keyword is used in Python to intentionally trigger an exception?

Question 2

What happens when a bare raise is executed inside an except block?

Question 3

How do you explicitly chain a new exception to an underlying causal exception?

Question 4

What is the effect of writing raise CustomError("Failed") from None?

Question 5

What error is raised if a programmer attempts to execute raise "Invalid Input"?

🚀 What's Next?

In the next lesson, we will continue your intermediate Python journey with Creating Custom Exceptions (6: Exception Handling).

👉 Continue to Next Lesson: Creating Custom Exceptions →

Next Lesson

Creating Custom Exceptions

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
Try-Except-Else-Finally	Creating Custom Exceptions

Practice Quiz

Test your understanding of this lesson with 5 questions. Each question has one correct answer.

Previous Next

PreviousPrevNext

MSK Institute • Shikohabad

Loading Page Content...

Preparing courses, live labs, and learning resources.सामग्री लोड हो रही है, कृपया प्रतीक्षा करें...

Connecting serverPlease wait...

💻 Practical Labs🚀 Free Demo📜 Verified Certificates

Creating Custom Exceptions

Raising Exceptions in Python

Intermediate8 min read•Updated: 2026-10-01

Study Materials Cheatsheet

Raising Exceptions in Python

1. The `raise` Statement

The raise keyword stops normal sequential execution and signals an exception. You can raise any instance or subclass of BaseException (almost always a subclass of Exception).

1def set_user_age(age: int):
2    if not isinstance(age, int):
3        raise TypeError(f"Age must be an integer, received {type(age).__name__}.")
4    if age < 0 or age > 130:
5        raise ValueError(f"Age {age} is out of realistic physiological range (0-130).")
6    
7    print(f"User age recorded: {age}")
8 
9set_user_age(28)
10 
11try:
12    set_user_age(-5)
13except ValueError as err:
14    print(f"Validation failed: {err}")

2. Re-raising Exceptions (Propagating After Logging)

Sometimes an except block needs to log diagnostic information, clean up temporary data, or execute metrics tracking, but still allow the exception to propagate to caller functions.

A bare raise statement inside an except clause re-raises the active exception currently being handled:

1import logging
2 
3def execute_remote_query(query: str):
4    try:
5        # Simulate network failure
6        raise ConnectionResetError("Connection lost to database cluster.")
7    except ConnectionResetError as err:
8        # 1. Log the failure locally
9        print(f"[AUDIT LOG] Database operation failed: {err}")
10        
11        # 2. Re-raise the active exception without losing original traceback!
12        raise
13 
14try:
15    execute_remote_query("SELECT * FROM orders")
16except ConnectionResetError:
17    print("Caller caught re-raised connection error.")

3. Exception Chaining: `raise ... from ...`

Python supports Exception Chaining using the from clause:

1class PaymentGatewayError(Exception):
  """Raised when a payment processor transaction fails."""
  pass
4 
5def charge_card(card_token: str, amount: float):
  try:
      # Low level network or crypto failure
      raise TimeoutError("Socket read timed out after 10000ms.")
  except TimeoutError as original_error:
      # Wrap the raw socket error inside a domain-specific PaymentGatewayError
      raise PaymentGatewayError("Payment could not be completed.") from original_error

When Python prints the traceback for this, it explicitly shows:

1The above exception was the direct cause of the following exception:
2PaymentGatewayError: Payment could not be completed.

The original error is preserved in the __cause__ attribute of the new exception.

4. Suppressing Context with `raise ... from None`

1def parse_security_pin(raw_pin: str) -> int:
  try:
      return int(raw_pin)
  except ValueError:
      # Hide the underlying ValueError traceback completely
      raise ValueError("PIN must consist of 4 to 6 numeric digits.") from None

Now, the traceback will only show ValueError: PIN must consist of 4 to 6 numeric digits. without the secondary "During handling of the above exception..." message.

5. Defensive Programming Best Practices

1
Always include informative error messages: Avoid raise ValueError(). Prefer raise ValueError(f"Expected positive price, got {price}").
2
Choose the most appropriate built-in exception:

Bad argument type: TypeError
Bad argument value/range: ValueError
Feature not ready: NotImplementedError
State violation: RuntimeError

1
Never raise strings: In modern Python, raise "Error" is a fatal TypeError. You must raise an Exception instance or class.

⚠️ Common Intermediate Mistakes & Gotchas

1. Raising String Literals

In modern Python, you must raise an instance or subclass of BaseException. Writing raise "Error" results in an immediate TypeError.

2. Losing Original Exception Tracebacks

When re-raising or transforming an exception, use raise NewException(...) from err to preserve the causal chain for easier debugging.

💻 Try It Yourself: Inventory Stock Guard

Scenario

Write a function dispense_item(inventory, item_name, count) that raises KeyError if the item is not in stock and ValueError if the requested count exceeds available stock.

Complete Solution

1def dispense_item(inventory: dict, item: str, count: int):
  if item not in inventory:
      raise KeyError(f"Item '{item}' is not tracked in inventory.")
  if count <= 0:
      raise ValueError("Requested count must be positive.")
  if count > inventory[item]:
      raise ValueError(f"Insufficient stock for '{item}'. Requested: {count}, Available: {inventory[item]}")
  
  inventory[item] -= count
  print(f"Dispensed {count}x '{item}'. Remaining: {inventory[item]}")
11 
12stock = {"Laptops": 5, "Mice": 20}
13try:
  dispense_item(stock, "Laptops", 3)
  dispense_item(stock, "Keyboards", 1)
16except (KeyError, ValueError) as err:
  print(f"Error caught: {err}")

Expected Output

1Dispensed 3x 'Laptops'. Remaining: 2
2Error caught: 'Item \'Keyboards\' is not tracked in inventory.'

Interactive Quiz• Knowledge Check

Practice Quiz

Question 1

Which keyword is used in Python to intentionally trigger an exception?

Question 2

What happens when a bare raise is executed inside an except block?

Question 3

How do you explicitly chain a new exception to an underlying causal exception?

Question 4

What is the effect of writing raise CustomError("Failed") from None?

Question 5

What error is raised if a programmer attempts to execute raise "Invalid Input"?

🚀 What's Next?

In the next lesson, we will continue your intermediate Python journey with Creating Custom Exceptions (6: Exception Handling).

👉 Continue to Next Lesson: Creating Custom Exceptions →

Next Lesson

Creating Custom Exceptions

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
Try-Except-Else-Finally	Creating Custom Exceptions

Practice Quiz

Test your understanding of this lesson with 5 questions. Each question has one correct answer.

Previous Next

Raising Exceptions in Python

1. The raise Statement

2. Re-raising Exceptions (Propagating After Logging)

3. Exception Chaining: raise ... from ...

4. Suppressing Context with raise ... from None

5. Defensive Programming Best Practices

⚠️ Common Intermediate Mistakes & Gotchas

1. Raising String Literals

2. Losing Original Exception Tracebacks

💻 Try It Yourself: Inventory Stock Guard

Scenario

Complete Solution

Expected Output

Practice Quiz

🚀 What's Next?

Creating Custom Exceptions

Related Lessons

Practice Quiz

Loading Page Content...

Raising Exceptions in Python

1. The raise Statement

2. Re-raising Exceptions (Propagating After Logging)

3. Exception Chaining: raise ... from ...

4. Suppressing Context with raise ... from None

5. Defensive Programming Best Practices

⚠️ Common Intermediate Mistakes & Gotchas

1. Raising String Literals

2. Losing Original Exception Tracebacks

💻 Try It Yourself: Inventory Stock Guard

Scenario

Complete Solution

Expected Output

Practice Quiz

🚀 What's Next?

Creating Custom Exceptions

Related Lessons

Practice Quiz

1. The `raise` Statement

3. Exception Chaining: `raise ... from ...`

4. Suppressing Context with `raise ... from None`

1. The `raise` Statement

3. Exception Chaining: `raise ... from ...`

4. Suppressing Context with `raise ... from None`