When would you build a pipeline with generators versus itertools versus a list?
PICTURE THIS: DOM IS A TREE
Simple meaning
Generators express custom lazy steps with local state.
WHY — Generators instead of guessing?
Why interviewers care about Generators:
contrast on Generators, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
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:
- 1Generators express custom lazy
steps with local state.
- 2itertools supplies C-speed building
blocks without per-item Python callbacks when they fit.
- 3Materialize a list only
at the end if the consumer needs random access or multiple passes, for example Django form choices.
- 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
Generators express custom lazy steps with local state. itertools supplies C-speed building blocks without per-item Python callbacks when they fit.