Get App

Python: What deeper point about Global Interpreter Lock (GIL) should a senior Python developer mention?

Difficulty:

Hard

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

What deeper point about Global Interpreter Lock (GIL) should a senior Python developer mention?

  1. A senior answer is precise about CPython, CPU-bound tradeoffs, and the difference between concurrency and parallel CPU execution.
  2. At senior level, the right answer is that Global Interpreter Lock (GIL) exists mostly for historical syntax reasons.
  3. At senior level, Python removes the tradeoffs around Global Interpreter Lock (GIL), so design choices barely matter in practice.
  4. At senior level, any approach to Global Interpreter Lock (GIL) is equally correct if it passes one small local test.

Hint

Look beyond syntax and explain the runtime, API, or design consequence.

Answer and rationale

Correct answer: A. A senior answer is precise about CPython, CPU-bound tradeoffs, and the difference between concurrency and parallel CPU execution.

A senior answer is precise about CPython, CPU-bound tradeoffs, and the difference between concurrency and parallel CPU execution. This is the kind of tradeoff-aware answer senior interviews usually expect.

Track: Python