Python dotenv: How load_dotenv() Reads Your .env File

You created your .env file in Module 03. Your API key is sitting there, stored safely, not in your code. Now: how does python-dotenv load env file data into your script? Four lines. Every AI script uses them. This lesson decodes all four.

Key Takeaways

• load_dotenv() reads your .env file and loads its values into environment variables, it does nothing if the file isn't found
• os.getenv("KEY") returns the value as a string, or None if the key doesn't exist
• The #1 beginner bug: calling load_dotenv() after you've already tried to read a variable
• .env is found relative to your terminal's current folder, not your script's folder
• Always check if not api_key: before using it, fail fast with a clear error, not a confusing one later

The four-line pattern

Here's the pattern you'll see at the top of almost every AI script you write or read:

from dotenv import load_dotenv
import os

load_dotenv()
api_key = os.getenv("ANTHROPIC_API_KEY")

Four lines. Let's decode each one.

Line 1: from dotenv import load_dotenv imports the function from the python-dotenv library (pip install python-dotenv, covered in Module 02).

Line 2: import os imports Python's standard os module. You need it for os.getenv(), the function that actually reads environment variables.

Line 3: load_dotenv() opens the .env file in your current working directory, reads every KEY=value pair inside it, and loads them into your process's environment. If .env doesn't exist, this line quietly does nothing, no crash, no warning.

Line 4: os.getenv("ANTHROPIC_API_KEY") reads that specific variable. Returns the string value if found, None if not. That's it, one function call, one variable assigned.

What breaks when a line is missing

Skip load_dotenv() and os.getenv() still runs, but it's reading an environment that was never populated. api_key becomes None, and your API call fails with an authentication error that has nothing to say about .env files at all. This is the most common silent bug in beginner AI scripts.

Skip the check on api_key and the failure just moves further downstream, from a clear "key not found" moment to a cryptic error buried inside whatever function tries to use None as a key.

Add the defensive check

Professional AI scripts don't stop at line four. They add a fifth:

if not api_key:
 raise ValueError("ANTHROPIC_API_KEY not found - check your .env file")

This fails fast, with a message that tells you exactly what to check. When you're reading someone else's code and this check is missing, that's your signal they haven't handled the missing-key edge case yet.

Order matters too: import → load → use. If you build your API client before load_dotenv() has run, api_key is still None at that point, it doesn't matter that the file gets loaded a line later.

Why "why is my api key None" happens so often

I've debugged this exact bug more times than I can count. Search "python dotenv" on any forum and the top complaint is always the same: os.getenv() returns None even though the key is clearly sitting in .env. It's almost never a typo in the key's value, it's one of four things:

That handoff, from your local .env file to a platform's own secret storage, is exactly what happens the day you deploy. Module 09 walks through how that works, once this same script is running on a live server instead of your laptop.

Your Task

pip install python-dotenv

from dotenv import load_dotenv
import os

load_dotenv()
api_key = os.getenv("ANTHROPIC_API_KEY")

if not api_key:
raise ValueError("ANTHROPIC_API_KEY not found - check your .env file")

print(api_key[:8])