Resource management

Safely open and write to a file while guaranteeing cleanup.

Writing text data to a file; logging output; saving results of computation.

Python scripts, data processing pipelines, any code that needs to write files.

with open(;, ;) as ;:

with open(;, ;) as ;:

filename: str or path-like object; mode: str like 'r', 'w', 'a', etc.; handle_var: identifier for the file object.

• write()
• read()
• close() (implicit)
• with statement
• try/except.

• Using open() without context manager and manual close(): risk of forgetting to close
• more verbose
• using pathlib.Path.open(): more modern path handling but similar semantics
• using tempfile.NamedTemporaryFile(): automatic cleanup and unique filename
• but file deleted on close
• using async with aiofiles.open(): async I/O
• requires async context
• nesting multiple with statements: allows multiple files but deeper nesting.

Failing to close the file leading to resource leaks: cause: forgetting to call close() or relying on garbage collection; consequence: file descriptor leak, potential data loss or corruption; Using the wrong mode causing overwrites: cause: opening with 'w' when intending to append; consequence: existing data truncated unexpectedly; Assuming file is closed after exception: cause: believing exception automatically closes file; consequence: resource leak if exception occurs before block ends.

Using open() with try/finally block: more verbose but explicit control; Using file.write() directly without context manager: less safe, no automatic cleanup.

Coming from C: forgetting to close files → rely on garbage collection; Coming from Java: using try-with-resources is analogous but syntax differs → use with statement.

• context manager
• resource acquisition is initialization (RAII)
• file I/O idioms

Do not use when you need to keep the file open beyond the block (e.g., returning the file object); Performance impact is negligible as file closing is I/O-bound; The file variable is inaccessible outside the block, and attempting to use it raises ValueError.

Guarantees proper resource cleanup, reducing bugs and improving code clarity.

Think 'with' as a blanket that wraps the file, keeping it safe.

Remember that the file handle is only valid inside the block; attempting to use it outside raises ValueError.

Using pathlib.Path('file.txt').open('w') as f: for more modern path handling.