Question 1

Why prefer 'with open()' over manual close()

Accepted Answer

File objects implement the context manager protocol (__enter__ and __exit__). When the 'with' block exits - whether normally or via an exception - __exit__ calls close() for you. Without 'with', a manual f.close() after a read that raises an exception is simply never reached. The file stays open, holding an OS file descriptor, until the garbage collector eventually reclaims the object. In a long-running process or tight loop this causes descriptor leaks that can hit the OS limit (ulimit -n, typically 1024 or 4096). The rule is simple: every open() belongs inside a 'with' block.

Question 2

readlines() vs iterating the file object

Accepted Answer

readlines() reads the entire file into memory and returns a Python list where each element is one line including its trailing newline character. So type(lines).__name__ is 'list' and len(lines) is 2. The alternative is to iterate the file object directly: 'for line in f:'. That approach is lazy - it reads one line at a time and uses constant memory no matter how large the file is. For data science work on multi-gigabyte logs or CSVs, iteration beats readlines() every time. Use readlines() only when you genuinely need random access to lines by index.

Question 3

open() modes: r, w, and a

Accepted Answer

'r' (read) is the default mode. The file must already exist or you get FileNotFoundError. 'w' (write) is the destructive one - if the file exists it is immediately truncated to zero bytes before you write a single character. If the file doesn't exist, Python creates it. 'a' (append) is the safe write mode: existing content is preserved and the file pointer starts at the end, so every write adds to the bottom. A quick way to remember: 'w' wipes, 'a' adds. If you ever lose data by accidentally using 'w' when you meant 'a', you'll remember the difference permanently.

Question 4

open() 'x' exclusive creation mode

Accepted Answer

The 'x' mode (exclusive creation) is a safety guard: it creates a new file and raises FileExistsError if the path is already taken. 'w' overwrites existing content without warning - which is easy to do accidentally. Use 'x' any time you are generating a unique output file and want to detect collisions rather than silently destroy previous work. A common pattern in data pipelines: write to a temp path with 'w', then rename it into place atomically - but for one-shot outputs, 'x' communicates intent clearly and fails loudly on mistakes.

Question 5

Iterating a file object vs readlines()

Accepted Answer

Iterating a file object is lazy - Python reads one line at a time from the OS buffer and discards it after your loop body runs. Only one line lives in memory at a time. f.readlines() loads the entire file into a list before the first iteration begins. For a 2 GB file that means 2 GB of memory consumed upfront. f.read().splitlines() is even worse - it first reads the whole file as a single string, then creates a second copy as a list of lines. When processing large files, direct iteration is not just a style preference - it's the difference between a script that works and one that crashes.