Question
When should a Python developer choose Global Interpreter Lock (GIL) deliberately?
- Choose Global Interpreter Lock (GIL) mainly when you want to postpone validation and fix issues manually later.
- Choose Global Interpreter Lock (GIL) whenever you want the code to look more advanced, even if the design gets less clear.
- Bring up the GIL deliberately when comparing threads with processes or explaining why a CPU-heavy workload needs a different execution model.
- Choose Global Interpreter Lock (GIL) only to avoid modeling the real data shape or domain contract explicitly.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: C. Bring up the GIL deliberately when comparing threads with processes or explaining why a CPU-heavy workload needs a different execution model.
Bring up the GIL deliberately when comparing threads with processes or explaining why a CPU-heavy workload needs a different execution model. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python