Files: Where Your Data Lives After the Program Stops

The problem...

Every program you've written so far has the same limitation.

You run it. You enter data. It processes. It prints.

Then you close it — and everything is gone.

The shopping list. The grades. The scores. Vanished.

Next time you run the program, you start from scratch.

In the field, that's not acceptable. A roster that resets every morning isn't a roster. It's a liability.

The idea!

Files let your program read data that already exists — and write data that will still be there tomorrow.

A text file on your computer is just a sequence of characters. Python can open it, read it, write to it, and close it.

That's file handling. And it's the closest thing to a database you'll use as a beginner.

Why this matters more than it looks

When your data lives in a file, something changes.

It survives. It can be backed up. It can be sent. It can be opened by another program, another person, another machine.

A .txt file with your shopping list is just a file — until you realize you can email it, sync it, version it, or feed it into another script.

A .csv file with grades can be opened in Excel, imported into a database, parsed by a web app, or attached to a report.

This is where Python stops being a calculator and starts being a tool.

Operating systems handle the rest: scheduled backups, file transfers, automated reports, access controls. Your script produces the file. The OS takes it from there.

What kinds of files

Python can work with many file types. In this chapter you'll focus on two:

• Text files (.txt) — plain text, one line at a time
• CSV files (.csv) — comma-separated values, the most common format for structured data

There are rules and options beyond what this chapter covers — encoding, binary files, JSON, file permissions. You'll encounter them as your projects grow. For now, these two formats cover most of what a beginner actually needs.

The basic pattern

Every file operation in Python follows the same structure:

1. Open the file
2. Do something with it — read or write
3. Close the file

Python gives you a clean way to handle all three steps at once:

with open("filename.txt", "r") as f:
    content = f.read()

with open() opens the file, gives you access to it as f, and closes it automatically when the block ends — even if something goes wrong.

This is the pattern you'll use. Always.

The mode

The second argument tells Python what you want to do with the file:

• "r" — read. The file must exist.
• "w" — write. Creates the file if it doesn't exist. Overwrites if it does.
• "a" — append. Adds to the end without touching what's already there.

You'll use all three. Each one does exactly one thing.

What's really happening

When you open a file, Python asks the operating system for access to it.

When you close it, Python releases that access.

If you don't close a file — it stays locked. with open() handles this for you automatically.

Heads up!

• File paths matter — if the file isn't where Python expects it, you get a FileNotFoundError
• "w" mode overwrites without warning — existing content is gone
• Always use with open() — it closes the file automatically
• By default, Python reads and writes text files in UTF-8 — this matters for special characters

The mindset shift

Stop thinking: "My program's data lives in variables."

Start thinking: "My program's data can live in files — persistent, readable, shareable, deployable."

What you should understand now

• Files let data persist after the program stops
• File handling is the beginner's first step toward real data persistence
• Use with open() — it opens and closes the file automatically
• "r" reads, "w" writes (overwrites), "a" appends
• Python works with text files and CSV files at beginner level
• Files integrate naturally with OS tools — backups, transfers, reports
• FileNotFoundError means the file path is wrong or the file doesn't exist