Get App

Python: Which practice avoids a common mistake with Global Interpreter Lock (GIL)?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Global Interpreter Lock (GIL)?

  1. Ignore the Global Interpreter Lock (GIL) issue and rely on team discipline instead of clearer APIs or invariants.
  2. Silence the Global Interpreter Lock (GIL) problem by using broad catches, hidden globals, or extra shared mutable state.
  3. Prefer the version of Global Interpreter Lock (GIL) that makes behavior less predictable as long as the code still runs.
  4. Do not oversimplify the GIL into 'threads are useless' because that misses real I/O overlap use cases and implementation nuance.

Hint

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

Answer and rationale

Correct answer: D. Do not oversimplify the GIL into 'threads are useless' because that misses real I/O overlap use cases and implementation nuance.

Do not oversimplify the GIL into 'threads are useless' because that misses real I/O overlap use cases and implementation nuance. This is a common failure mode in real Python code and a frequent interview follow-up.

Track: Python