Get App

Python: Which practice avoids a common mistake with pathlib and File I/O?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with pathlib and File I/O?

  1. Ignore the pathlib and File I/O issue and rely on team discipline instead of clearer APIs or invariants.
  2. Silence the pathlib and File I/O problem by using broad catches, hidden globals, or extra shared mutable state.
  3. Do not treat file I/O as harmless just because the code is short; boundaries like encoding, existence, and partial writes still matter.
  4. Prefer the version of pathlib and File I/O that makes behavior less predictable as long as the code still runs.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: C. Do not treat file I/O as harmless just because the code is short; boundaries like encoding, existence, and partial writes still matter.

Do not treat file I/O as harmless just because the code is short; boundaries like encoding, existence, and partial writes still matter. This is a common failure mode in real Python code and a frequent interview follow-up.

Track: Python