File I/O

Ensures automatic file handle cleanup and consistent UTF-8 decoding when reading text files across platforms.

Data processing: reading CSV or JSON configuration files with known UTF-8 content. Cross-platform scripts: avoiding Windows cp1252 vs Linux UTF-8 default encoding mismatch. Log analysis: safely iterating over large log files that must be closed promptly after use.

Common in data processing scripts, configuration loaders, log readers, or any script that reads text files.

from pathlib import Path; with Path(filepath).open(mode, encoding=encoding) as handle:

from pathlib import Path; with Path(...).open(..., encoding=...) as ...:

filepath: str or Path object, mode: str such as 'r' or 'w', encoding: str such as 'utf-8', handle: file-like object

• Path.read_text()
• Path.write_text()
• csv.reader
• json.load
• for line in handle

• built-in open(filepath
• mode
• encoding=encoding): avoids pathlib dependency but loses Path chaining benefits. Path.read_text(encoding=encoding): simpler for small files that fit in memory but loads entire content at once. Path.read_bytes(): for binary files where encoding is irrelevant.

forgetting to use the with statement and forgetting to close the file using the built‑in open() instead of Path.open() omitting the encoding argument which can cause platform‑dependent decoding errors using the wrong mode (e.g., 'w' for writing) when intending to read attempting to write to the file after the with block ends

built-in open(): standalone function without Path object chaining. Path.read_text(): reads entire file into a string without context manager. Path.read_bytes(): reads binary content, no encoding parameter needed.

Coming from C: manual fclose() calls are unnecessary inside a with block — Python's context manager handles closure automatically. Coming from Java: try-finally resource management is replaced by the with-statement in Python. Coming from Python 2: implicit encoding is not guaranteed — always specify encoding explicitly for portability.

• with open()
• Path.read_text()
• Path.write_text()
• Path.open()
• contextlib.closing

Do not use this when the entire file content fits in memory — prefer Path.read_text() for simplicity. The with-statement adds negligible overhead; the real cost is the I/O itself. On Windows, omitting encoding defaults to cp1252 while on Linux it defaults to UTF-8, making the encoding parameter essential for cross-platform code.

Prevents file handle leaks in long-running processes and eliminates an entire class of encoding-related UnicodeDecodeError bugs that are difficult to reproduce across operating systems.

Like hiring a librarian who checks the book back in automatically — Path.open gives you the file, and the with-statement guarantees it gets closed no matter what happens while you read.

Path.open() accepts the same arguments as the built-in open() function; the only difference is that it is called as a method on a Path object, enabling method chaining with other pathlib operations.

Path.read_text(encoding='utf-8') for simple whole-file reads, or Path.iterdir() combined with open for batch file processing.