File Exceptions and Error Handling in Python0%

Modern Filesystem Handling with pathlib.Path

File Exceptions and Error Handling in Python

Intermediate8 min read•Updated: 2026-10-01

File Exceptions and Error Handling in Python

File operations interact directly with the operating system and physical storage drives, making them inherently prone to runtime exceptions. A file might be missing, locked by another process, lack read/write permissions, or contain an incompatible text encoding.

Mastering Python's file exception hierarchy ensures your applications fail gracefully and protect critical user data from corruption.

1. The File Exception Hierarchy

All file and operating-system-level errors in Python inherit from the base OSError class.

1BaseException
└── Exception
    └── OSError (or EnvironmentError / IOError)
         ├── FileNotFoundError       # File does not exist
         ├── PermissionError         # Insufficient read/write privileges
         ├── IsADirectoryError       # Expected a file, but target is a folder
         ├── NotADirectoryError      # Expected a directory in path, but found a file
         ├── FileExistsError         # Attempted to create an already-existing file (mode 'x')
         └── TimeoutError            # System operation timed out

Additionally, opening text files with the wrong character set can trigger:

UnicodeDecodeError: Occurs when bytes in a binary stream cannot be decoded into the expected encoding (e.g., attempting to read a binary image as utf-8).
UnicodeEncodeError: Occurs when writing characters that the target encoding cannot express.

2. Common File Exceptions in Action

1. `FileNotFoundError`

Attempting to read a non-existent file in 'r' mode raises FileNotFoundError:

1try:
2    with open("missing_report.csv", "r", encoding="utf-8") as f:
3        data = f.read()
4except FileNotFoundError as err:
5    print(f"Error: Could not locate file ({err})")

2. `PermissionError`

Occurs when the current user account does not have read/write privileges for the destination path, or if an operating-system-level lock (e.g., another process writing to the file) prohibits access:

1try:
2    # Attempting to write to a protected system folder
3    with open("C:/Windows/System32/config.sys", "w") as f:
4        f.write("test")
5except PermissionError:
6    print("Access denied: Administrative privileges required.")

3. `FileExistsError` (Exclusive Creation Mode `'x'`)

Mode 'x' guarantees that a file is created only if it does not already exist, preventing accidental data overwrites:

1try:
2    with open("audit_log.txt", "x", encoding="utf-8") as f:
3        f.write("Log initialized.\n")
4except FileExistsError:
5    print("Audit log already exists. Skipping re-initialization.")

3. The Full `try-except-else-finally` File Pattern

The most robust architectural pattern for file operations combines context managers with a comprehensive error-handling structure:

1def process_data_file(filepath):
  file_handle = None
  try:
      # 1. Attempt the file operation
      with open(filepath, "r", encoding="utf-8") as file_handle:
          content = file_handle.read()
          processed_data = [line.strip().upper() for line in content.splitlines()]
          
  except FileNotFoundError:
      print(f"Error: Target file '{filepath}' was not found.")
      return None
      
  except PermissionError:
      print(f"Error: Insufficient read permissions for '{filepath}'.")
      return None
      
  except UnicodeDecodeError as err:
      print(f"Encoding mismatch in '{filepath}': {err}")
      return None
      
  except OSError as err:
      # Catch-all for any other low-level OS/disk failures
      print(f"Unexpected OS error occurred: {err}")
      return None
      
  else:
      # 2. Runs ONLY if try block executed without any exceptions
      print(f"Successfully processed {len(processed_data)} records.")
      return processed_data
      
  finally:
      # 3. Runs ALWAYS, regardless of success or exception
      print(f"File handling cycle for '{filepath}' concluded.")

4. EAFP vs. LBYL in File Handling

In Python development, there are two distinct design philosophies:

1
LBYL (Look Before You Leap):

 import os
 if os.path.exists("records.txt"):
     with open("records.txt") as f:
         data = f.read()

The Flaw: Race conditions (TOCTOU - Time Of Check To Time Of Use). Between the time os.path.exists() returns True and open() executes, another process or thread could delete or lock the file!

1
EAFP (Easier to Ask for Forgiveness than Permission - The Pythonic Way):

 try:
     with open("records.txt") as f:
         data = f.read()
 except FileNotFoundError:
     data = ""

The Benefit: Atomic, clean, thread-safe, and avoids redundant filesystem calls.

5. Best Practices Checklist

Always handle specific exceptions first: Place FileNotFoundError and PermissionError before generic OSError or Exception.
Always specify encoding="utf-8": Never rely on system-default encodings (which differ between Windows and Linux/macOS).
Use mode 'x' for safety: If you don't want to inadvertently overwrite existing files, use exclusive creation 'x'.
Embrace EAFP: Let open() attempt the action and catch expected errors rather than pre-checking with os.path.exists().

⚠️ Common Intermediate Mistakes & Gotchas

1. Not Specifying `encoding="utf-8"`

Relying on platform-default encoding leads to silent corruption or UnicodeDecodeError when moving code between Windows (which often defaults to cp1252) and Linux (UTF-8). Always declare encoding="utf-8".

2. Catching Generic `Exception` Too Early

Catching Exception before specific file exceptions (FileNotFoundError, PermissionError) hides the root cause. Catch specific errors first, with generic exceptions as a fallback.

💻 Try It Yourself: Resilient File Reader Utility

Scenario

Write a utility function read_file_safe(filepath) that gracefully handles FileNotFoundError, PermissionError, and UnicodeDecodeError with descriptive error logs without crashing the program.

Starter Code

1# TODO: Implement read_file_safe function handling specific file exceptions

Complete Solution

1import os
2 
3def read_file_safe(filepath):
4    try:
5        with open(filepath, "r", encoding="utf-8") as f:
6            return f.read()
7    except FileNotFoundError:
8        print(f"[ERROR] The file '{filepath}' does not exist.")
9    except PermissionError:
10        print(f"[ERROR] Permission denied to read '{filepath}'.")
11    except UnicodeDecodeError as err:
12        print(f"[ERROR] Encoding mismatch while reading '{filepath}': {err}")
13    except Exception as err:
14        print(f"[UNEXPECTED ERROR] An error occurred: {err}")
15    return None
16 
17# Test with a non-existent file
18result = read_file_safe("non_existent_records.txt")
19print("Execution resumed normally without crash.")

Expected Output

1[ERROR] The file 'non_existent_records.txt' does not exist.
2Execution resumed normally without crash.

Interactive Quiz• Knowledge Check

Practice Quiz

Question 1

Which base class do FileNotFoundError, PermissionError, and IsADirectoryError all inherit from?

Question 2

What open mode should you use to open a file for writing ONLY if the file does not already exist?

Question 3

Why is the EAFP pattern preferred over checking os.path.exists() before opening a file?

Question 4

Which block in a try-except-else-finally statement executes strictly when NO exceptions occurred in the try block?

Question 5

What error occurs when reading a file encoded in UTF-16 using encoding="utf-8"?

🚀 What's Next?

In the next lesson, we will continue your intermediate Python journey with Project: CSV Contact Manager (4: File Handling Advanced).

👉 Continue to Next Lesson: Project: CSV Contact Manager →

Next Lesson

Modern Filesystem Handling with pathlib.Path

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

Related Lessons

Previous Lesson	Next Lesson
Working with JSON Files	Modern Filesystem Handling with pathlib.Path

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

Modern Filesystem Handling with pathlib.Path

File Exceptions and Error Handling in Python

Intermediate8 min read•Updated: 2026-10-01

Study Materials Cheatsheet

File Exceptions and Error Handling in Python

Mastering Python's file exception hierarchy ensures your applications fail gracefully and protect critical user data from corruption.

1. The File Exception Hierarchy

All file and operating-system-level errors in Python inherit from the base OSError class.

1BaseException
└── Exception
    └── OSError (or EnvironmentError / IOError)
         ├── FileNotFoundError       # File does not exist
         ├── PermissionError         # Insufficient read/write privileges
         ├── IsADirectoryError       # Expected a file, but target is a folder
         ├── NotADirectoryError      # Expected a directory in path, but found a file
         ├── FileExistsError         # Attempted to create an already-existing file (mode 'x')
         └── TimeoutError            # System operation timed out

Additionally, opening text files with the wrong character set can trigger:

UnicodeDecodeError: Occurs when bytes in a binary stream cannot be decoded into the expected encoding (e.g., attempting to read a binary image as utf-8).
UnicodeEncodeError: Occurs when writing characters that the target encoding cannot express.

2. Common File Exceptions in Action

1. `FileNotFoundError`

Attempting to read a non-existent file in 'r' mode raises FileNotFoundError:

1try:
2    with open("missing_report.csv", "r", encoding="utf-8") as f:
3        data = f.read()
4except FileNotFoundError as err:
5    print(f"Error: Could not locate file ({err})")

2. `PermissionError`

Occurs when the current user account does not have read/write privileges for the destination path, or if an operating-system-level lock (e.g., another process writing to the file) prohibits access:

1try:
2    # Attempting to write to a protected system folder
3    with open("C:/Windows/System32/config.sys", "w") as f:
4        f.write("test")
5except PermissionError:
6    print("Access denied: Administrative privileges required.")

3. `FileExistsError` (Exclusive Creation Mode `'x'`)

Mode 'x' guarantees that a file is created only if it does not already exist, preventing accidental data overwrites:

1try:
2    with open("audit_log.txt", "x", encoding="utf-8") as f:
3        f.write("Log initialized.\n")
4except FileExistsError:
5    print("Audit log already exists. Skipping re-initialization.")

3. The Full `try-except-else-finally` File Pattern

The most robust architectural pattern for file operations combines context managers with a comprehensive error-handling structure:

1def process_data_file(filepath):
  file_handle = None
  try:
      # 1. Attempt the file operation
      with open(filepath, "r", encoding="utf-8") as file_handle:
          content = file_handle.read()
          processed_data = [line.strip().upper() for line in content.splitlines()]
          
  except FileNotFoundError:
      print(f"Error: Target file '{filepath}' was not found.")
      return None
      
  except PermissionError:
      print(f"Error: Insufficient read permissions for '{filepath}'.")
      return None
      
  except UnicodeDecodeError as err:
      print(f"Encoding mismatch in '{filepath}': {err}")
      return None
      
  except OSError as err:
      # Catch-all for any other low-level OS/disk failures
      print(f"Unexpected OS error occurred: {err}")
      return None
      
  else:
      # 2. Runs ONLY if try block executed without any exceptions
      print(f"Successfully processed {len(processed_data)} records.")
      return processed_data
      
  finally:
      # 3. Runs ALWAYS, regardless of success or exception
      print(f"File handling cycle for '{filepath}' concluded.")

4. EAFP vs. LBYL in File Handling

In Python development, there are two distinct design philosophies:

1
LBYL (Look Before You Leap):

 import os
 if os.path.exists("records.txt"):
     with open("records.txt") as f:
         data = f.read()

1
EAFP (Easier to Ask for Forgiveness than Permission - The Pythonic Way):

 try:
     with open("records.txt") as f:
         data = f.read()
 except FileNotFoundError:
     data = ""

The Benefit: Atomic, clean, thread-safe, and avoids redundant filesystem calls.

5. Best Practices Checklist

Always handle specific exceptions first: Place FileNotFoundError and PermissionError before generic OSError or Exception.
Always specify encoding="utf-8": Never rely on system-default encodings (which differ between Windows and Linux/macOS).
Use mode 'x' for safety: If you don't want to inadvertently overwrite existing files, use exclusive creation 'x'.
Embrace EAFP: Let open() attempt the action and catch expected errors rather than pre-checking with os.path.exists().

⚠️ Common Intermediate Mistakes & Gotchas

1. Not Specifying `encoding="utf-8"`

2. Catching Generic `Exception` Too Early

Catching Exception before specific file exceptions (FileNotFoundError, PermissionError) hides the root cause. Catch specific errors first, with generic exceptions as a fallback.

💻 Try It Yourself: Resilient File Reader Utility

Scenario

Write a utility function read_file_safe(filepath) that gracefully handles FileNotFoundError, PermissionError, and UnicodeDecodeError with descriptive error logs without crashing the program.

Starter Code

1# TODO: Implement read_file_safe function handling specific file exceptions

Complete Solution

1import os
2 
3def read_file_safe(filepath):
4    try:
5        with open(filepath, "r", encoding="utf-8") as f:
6            return f.read()
7    except FileNotFoundError:
8        print(f"[ERROR] The file '{filepath}' does not exist.")
9    except PermissionError:
10        print(f"[ERROR] Permission denied to read '{filepath}'.")
11    except UnicodeDecodeError as err:
12        print(f"[ERROR] Encoding mismatch while reading '{filepath}': {err}")
13    except Exception as err:
14        print(f"[UNEXPECTED ERROR] An error occurred: {err}")
15    return None
16 
17# Test with a non-existent file
18result = read_file_safe("non_existent_records.txt")
19print("Execution resumed normally without crash.")

Expected Output

1[ERROR] The file 'non_existent_records.txt' does not exist.
2Execution resumed normally without crash.

Interactive Quiz• Knowledge Check

Practice Quiz

Question 1

Which base class do FileNotFoundError, PermissionError, and IsADirectoryError all inherit from?

Question 2

What open mode should you use to open a file for writing ONLY if the file does not already exist?

Question 3

Why is the EAFP pattern preferred over checking os.path.exists() before opening a file?

Question 4

Which block in a try-except-else-finally statement executes strictly when NO exceptions occurred in the try block?

Question 5

What error occurs when reading a file encoded in UTF-16 using encoding="utf-8"?

🚀 What's Next?

In the next lesson, we will continue your intermediate Python journey with Project: CSV Contact Manager (4: File Handling Advanced).

👉 Continue to Next Lesson: Project: CSV Contact Manager →

Next Lesson

Modern Filesystem Handling with pathlib.Path

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

Related Lessons

Previous Lesson	Next Lesson
Working with JSON Files	Modern Filesystem Handling with pathlib.Path

Practice Quiz

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

Previous Next

File Exceptions and Error Handling in Python

1. The File Exception Hierarchy

2. Common File Exceptions in Action

1. FileNotFoundError

2. PermissionError

3. FileExistsError (Exclusive Creation Mode 'x')

3. The Full try-except-else-finally File Pattern

4. EAFP vs. LBYL in File Handling

5. Best Practices Checklist

⚠️ Common Intermediate Mistakes & Gotchas

1. Not Specifying encoding="utf-8"

2. Catching Generic Exception Too Early

💻 Try It Yourself: Resilient File Reader Utility

Scenario

Starter Code

Complete Solution

Expected Output

Practice Quiz

🚀 What's Next?

Modern Filesystem Handling with pathlib.Path

Related Lessons

Practice Quiz

Loading Page Content...

File Exceptions and Error Handling in Python

1. The File Exception Hierarchy

2. Common File Exceptions in Action

1. FileNotFoundError

2. PermissionError

3. FileExistsError (Exclusive Creation Mode 'x')

3. The Full try-except-else-finally File Pattern

4. EAFP vs. LBYL in File Handling

5. Best Practices Checklist

⚠️ Common Intermediate Mistakes & Gotchas

1. Not Specifying encoding="utf-8"

2. Catching Generic Exception Too Early

💻 Try It Yourself: Resilient File Reader Utility

Scenario

Starter Code

Complete Solution

Expected Output

Practice Quiz

🚀 What's Next?

Modern Filesystem Handling with pathlib.Path

Related Lessons

Practice Quiz

1. `FileNotFoundError`

2. `PermissionError`

3. `FileExistsError` (Exclusive Creation Mode `'x'`)

3. The Full `try-except-else-finally` File Pattern

1. Not Specifying `encoding="utf-8"`

2. Catching Generic `Exception` Too Early

1. `FileNotFoundError`

2. `PermissionError`

3. `FileExistsError` (Exclusive Creation Mode `'x'`)

3. The Full `try-except-else-finally` File Pattern

1. Not Specifying `encoding="utf-8"`

2. Catching Generic `Exception` Too Early