Bring One Local Result Back

You have already seen the privacy boundary. Read it once more immediately before the checker command:

pl_check.py runs on this computer. The script itself makes no network requests and never uploads anything. It runs only the listed checks; a declared package import executes that curated package’s import code. Its token contains the chapter and plan versions, exact Python version, pass/fail-style environment facts, declared relative file names, and file content digests; never absolute paths, usernames, environment variables, or file contents. When you paste and submit the token, Python Land receives and may store it as lesson work.

For Chapter 4 plan 2, the listed checks are:

1. Python 3.10 or newer ran the checker.

2. That Python was inside a virtual environment.

3. That Python could import requests.

4. hello.py exactly matched the reviewed one-line program.

5. requirements.txt exactly contained requests==2.34.2.

The checker reads only those two declared relative files, with a 64 KiB limit. It does not read shell history or editor settings.

Run with the selected interpreter

Use the activation-free route first. It is the least ambiguous one:

./.venv/bin/python ./pl_check.py chapter-4

.\.venv\Scripts\python.exe .\pl_check.py chapter-4

./.venv/bin/python ./pl_check.py chapter-4

The script prints its privacy notice first, then one status line per check. Copy the complete final line beginning with PL_CHECK_TOKEN=.

In the editor beside this lesson, replace only the placeholder text between the triple quotes. Leave USE_SITE_ONLY_PATH = False, then press Submit.

A passing result means only that the selected local Python ran the checker and reported those five declared facts. Python Land did not inspect your computer directly. The token does not prove that you clicked an editor setting or ran hello.py; you observed those steps yourself.

If a check fails

Read the first not met line and use its next action. Common recoveries are:

• run the checker from the extracted project root, beside the three authored files;

• use the explicit .venv interpreter path rather than a global Python;

• reinstall the recipe with that interpreter’s -m pip;

• restore hello.py or requirements.txt from the ZIP if its exact content changed.

Run the checker again after the repair and paste the new complete line. Do not turn a failed token into fallback; failed and malformed tokens remain failed submissions.

The explicit site-only path

Use the site-only path when Python cannot be installed or run, the computer is managed, download or unzip is blocked, or an accessibility or support need makes the local route impractical.

In the editor, set exactly:

USE_SITE_ONLY_PATH = True

Then press Submit. The recorded outcome says:

Site-only path selected: completion is recorded, but no local machine was verified.

That is a continuation path, not local verification. You can return later, set the value back to False, and submit a current passing token.