Question 700
A production wheel installs but its entry point fails because the project uses a flat source tree with accidental imports. Which principle BEST explains why the implementation failed?
Explanation
Correct Answer
Import behavior in a working directory can mask packaging omissions in a built artifact. This is the most directly relevant technical explanation because import behavior in a working directory can mask packaging omissions in a built artifact. A concrete acceptance check is: The wheel installs and imports correctly in a fresh Python environment. To reduce recurrence: Build and test distributions outside the source directory.
Incorrect Answers
Unconstrained transitive versions can introduce incompatible behavior between environments. That consideration does not remove the current constraint: import behavior in a working directory can mask packaging omissions in a built artifact.
Continuous partial streams may expose results before all expected daily inputs arrive. For the observed behavior, import behavior in a working directory can mask packaging omissions in a built artifact.
Null field values and explicit source delete operations have different meanings. The controlling issue in this question is that import behavior in a working directory can mask packaging omissions in a built artifact.