Question
Which practice avoids a common mistake with Threading, asyncio, and multiprocessing?
- Ignore the Threading, asyncio, and multiprocessing issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Threading, asyncio, and multiprocessing problem by using broad catches, hidden globals, or extra shared mutable state.
- Do not describe all concurrency tools as interchangeable because their cancellation, overhead, and scaling characteristics differ sharply.
- Prefer the version of Threading, asyncio, and multiprocessing that makes behavior less predictable as long as the code still runs.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: C. Do not describe all concurrency tools as interchangeable because their cancellation, overhead, and scaling characteristics differ sharply.
Do not describe all concurrency tools as interchangeable because their cancellation, overhead, and scaling characteristics differ sharply. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python