Why did CPython historically keep a GIL?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
The GIL made reference counting and C-API thread safety much simpler, which helped CPython grow extensions quickly.
WHY — GIL instead of guessing?
Why interviewers care about GIL:
on GIL.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1The GIL made reference
counting and C-API thread safety much simpler, which helped CPython grow extensions quickly.
- 2Removing it required a
different object memory model and a long migration of the C API.
- 3That tradeoff favored single-thread
speed and extension ease over multi-core Python-level parallelism.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
The GIL made reference counting and C-API thread safety much simpler, which helped CPython grow extensions quickly. Removing it required a different object memory model and a long migration of the C API.