Course contentsShow
← Python
Lesson 343 of 1,0606. Error Handling and File I/OFree lesson

Executing Cleanup Code With Finally Blocks

Ensure critical cleanup operations execute regardless of whether an error occurred by utilizing the finally block in your exception handling.

Executing Cleanup Code With Finally Blocks

In this lesson, you will learn how to use the finally block to guarantee that essential cleanup code runs even when errors interrupt your program.

Why Cleanup Matters

When you work with external resources—like opening a file to read data or connecting to a database—it is vital to close those resources properly once you are finished. If your code encounters an error while processing that file, the program might crash, leaving the file "locked" or causing a memory leak.

In basic try-except blocks, if an exception is raised, the lines of code immediately following it are skipped. If you put your "close file" code after the try-except block, it might never run during a crash. The finally block solves this by acting as a safety net.

How It Works

The finally block is attached to your try-except structure. Code inside this block is guaranteed to run no matter what happens inside the try block—whether the code succeeds, throws an exception that is caught, or even throws an exception that isn't caught.

file = open("data.txt", "r")

try:
    content = file.read()
    # Imagine a potential error here, like a division by zero
    result = 10 / 0 
except ZeroDivisionError:
    print("Caught an error while reading!")
finally:
    # This will execute even if the error above occurs
    file.close()
    print("File has been closed safely.")

In the example above, even though the program hits a ZeroDivisionError, the finally block ensures the file.close() method is executed before the program terminates. This keeps your system resources healthy and prevents data corruption.

Think of finally as the "no matter what" section of your code. It is the perfect place for closing connections, releasing locks, or printing a final status message to ensure your application finishes its housekeeping duties before exiting a task.

Key Takeaway: Use the finally block to ensure that critical cleanup tasks—like closing files or network connections—run reliably, regardless of whether your code succeeded or crashed.