Resource guide

Your Python environment

Choose a native environment

Use PowerShell with a Windows Python interpreter, or Bash with a Linux interpreter. Start Project 001 without containers or remote machines so the network context is easy to describe. WSL is optional and should be recorded as Linux under WSL.

Verify the selected interpreter

Run its version command before the lesson. If several Python versions exist, invoke the interpreter by its explicit environment path. In an editor, select that same interpreter. An editor's run button may otherwise choose a different installation than your terminal.

Use isolated environments when useful

A venv separates package installation from other projects. It is disposable and tied to the OS and interpreter used to create it. Keep your source outside it. Add .venv and __pycache__ to version-control exclusions. When dependencies are introduced later, install them with the selected interpreter's -m pip and record their versions.

Keep the first project simple

Project 001 uses the standard library, so an environment is optional. No package installation is required after Python itself is available. uv can select the requested Python version; the standard venv method teaches an equally usable baseline.

Reproduce, then diagnose

Write down the working directory, interpreter version, command, input files, and exact error. Change one variable at a time. Do not repair an ordinary project-folder problem by weakening machine-wide permissions or changing shell security policy.

Apply this in the complete free Project 001 lesson →

Search PythonProjects.org