Question 200
A production wheel installs but its entry point fails because the project uses a flat source tree with accidental imports. Which change most directly addresses the operational problem?
Explanation
Correct Answer
Adopt a declared src-layout package and explicit module entry points in the build metadata. This is the most directly relevant remediation 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
Job orchestration does not make all independent writes one global ACID transaction. Here the important technical distinction is that import behavior in a working directory can mask packaging omissions in a built artifact.
Interactive compute libraries are not implicitly present on new job compute. The reported failure instead depends on this fact: import behavior in a working directory can mask packaging omissions in a built artifact.
Coupling unit logic to live tables creates avoidable data mutation and flaky tests. That consideration does not remove the current constraint: import behavior in a working directory can mask packaging omissions in a built artifact.