Solving Python's 'FileNotFoundError: [Errno 2]' Once and For All

The Frustrating Reality of File Paths

It’s a classic scenario. You have a data.csv file sitting in the exact same folder as your main.py script. You run the code, expecting a smooth import, but Python insists the file doesn't exist. This usually happens because your terminal is "standing" in a different directory than your script.

The error looks like this and it can halt your workflow instantly:

FileNotFoundError: [Errno 2] No such file or directory: 'data.csv'

The Hidden Reason: Your Working Directory

The most frequent cause isn't a missing file; it’s a misunderstood Current Working Directory (CWD). When you use a relative path like 'data.csv', Python doesn't look where the script lives. Instead, it looks in the directory where you launched the command.

Imagine your script is in C:/Projects/App/script.py. If your terminal is open at C:/Users/Admin/ and you run python Projects/App/script.py, Python will look for the data in C:/Users/Admin/data.csv. It won't find it.

Other usual suspects include:

• Hidden extensions: Your file is actually named data.csv.csv because Windows hid the known extension.
• Case sensitivity: Data.csv and data.csv are different files on Linux and macOS.
• Escape characters: Using single backslashes in Windows paths (like "C:\users\name") often triggers errors.

The Quick Diagnostic

Before you change your file structure, see exactly where Python is looking. Add these lines to the very top of your script to reveal the truth:

import os
print(f"Python is currently looking in: {os.getcwd()}")

If that path doesn't match your file's location, your relative paths will fail every time. You can bypass this immediately by using a full absolute path, though it's less portable:

# Hardcoded path for a quick test
with open('/Users/alex/projects/data/config.json', 'r') as f:
    print(f.read())

The Best Fix: Pathlib (The Modern Standard)

The pathlib module is the smartest way to handle files in modern Python. It treats paths as objects rather than strings, making them much easier to manipulate. To find a file relative to your script—no matter where you run it from—use this pattern:

from pathlib import Path

# Find the folder where this script actually lives
BASE_DIR = Path(__file__).resolve().parent

# Join the folder with your filename safely
file_path = BASE_DIR / "data" / "results.csv"

with open(file_path, 'r') as f:
    data = f.read()

The Reliable 'os' Method

If you are working on a legacy codebase or prefer the os module, you can still build dynamic paths. This method calculates the absolute path to your script at runtime, ensuring the file is found even if you move the project folder.

import os

# Calculate the directory of the current file
script_dir = os.path.dirname(os.path.abspath(__file__))
file_path = os.path.join(script_dir, 'data', 'results.csv')

if os.path.exists(file_path):
    with open(file_path, 'r') as f:
        print("File found and opened successfully!")
else:
    print(f"Search failed at: {file_path}")

A Note on Windows Backslashes

Windows paths are notorious for bugs because \ is an escape character. For example, "C:\new\test.txt" fails because \n is interpreted as a newline. You have two clean ways to fix this:

• Raw Strings: Put an r before the quotes: r"C:\users\data.txt".
• Forward Slashes: Use "C:/users/data.txt". Python handles this perfectly on Windows.

Final Checklist

• Print the path: Always print your final path variable before calling open() to see exactly what Python sees.
• Verify the extension: Check your file properties to ensure you haven't accidentally named a file script.py.txt.
• Check permissions: Ensure your user account has read access to the target folder.