Question
Which practice avoids a common mistake with Virtual Environments, pip, and pyproject.toml?
- Ignore the Virtual Environments, pip, and pyproject.toml issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Virtual Environments, pip, and pyproject.toml problem by using broad catches, hidden globals, or extra shared mutable state.
- Do not rely on globally installed packages or tribal setup knowledge when the project needs repeatable builds and onboarding.
- Prefer the version of Virtual Environments, pip, and pyproject.toml 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 rely on globally installed packages or tribal setup knowledge when the project needs repeatable builds and onboarding.
Do not rely on globally installed packages or tribal setup knowledge when the project needs repeatable builds and onboarding. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python