Three Files, One Project

Before this project leaves the browser, here is exactly what its local checker does and what later submission sends.

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.

You decide whether to run the checker and whether to paste its result. Python Land cannot reach into your computer, and a token is not remote access.

One folder is the project boundary

The project editor beside this lesson shows three files:

hello.py
pl_check.py
requirements.txt

They belong together. hello.py is the small program. requirements.txt is the durable package recipe from Chapter 3. pl_check.py is a standalone course tool that will inspect only the checks listed again in the final lesson.

The folder is the project. None of these files is “inside” the editor; the editor is one view of the folder. A terminal will be another view of the same folder on your machine.

Rehearse the run here

The editor has opened hello.py, the chapter’s entry file. Press Run in the project toolbar. It prints:

Hello from your own machine!

That run happens in the browser, not on your computer. It proves the file is valid and gives you a result to recognize later. It does not prove anything about a local Python installation.

The next lesson downloads the whole project. Do not copy only the visible line of Python; the point is to keep the three-file folder together.