Unit 2 Checkpoint: Prove the Environment

Imagine somebody opens your project and says, “Python is broken.”

Use your own environment evidence to replace that vague claim with a better diagnosis.

Include:

• the path to the file you intended to run;
• the directory the terminal was actually using;
• one piece of evidence identifying the Python runtime or interpreter; and
• one mismatch that could make correct source code appear not to work.

Then write a two-step diagnostic you would perform before reinstalling anything.

The strongest response points to observable state, not interface guesses.