Environment and files
Environments and files keep a project self-contained — code, data and dependencies in known places, so the project runs on another machine too.
Python for Kids · Class 9 · Module 1 of 9
Professional Python Foundations
Time to work the way professionals actually work.
8 sessionsSessions 1–8
4 weeksTypical pace
Intermediate to AppliedLevel
Class 9Python & Coding
The big idea
Students move beyond single-file scripts into proper project structure: organised files, a consistent environment, disciplined style and a systematic approach to finding faults rather than a hopeful one.
Why it matters
Class 9 introduces databases, web apps and APIs. None of them are pleasant without solid working habits in place first.
Unpacked
What you will actually learn
Three core ideas, each taught with worked examples and then practised until it feels obvious.
Style
Style follows PEP 8, Python’s official guide. Following a shared standard means any Python programmer can read your work immediately.
Debugging
Debugging becomes systematic: reproduce reliably, narrow the search, inspect real values, change one thing, verify. Never two changes at once.
Did you know?
PEP 8 is itself a numbered proposal document, part of a public process anyone can contribute to. Python’s rules are written in the open.
Common mix-up
“Everything can live in one file.” It can, until it cannot — and untangling a 900-line file late in a project is genuinely painful.
Session by session
Your 8-session journey
Sessions 1–8 of the 72-session year, at two one-hour sessions per week.
- 1
Warm-up and big picture
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about environment and files.
- 2
Environment and files
Guided teaching on environment and files, worked through together with the teacher.
- 3
Environment and files — practice lab
Independent practice, small challenges and one deliberate mistake to diagnose.
- 4
Style
Guided teaching on style, building directly on the previous two sessions.
- 5
Style — practice lab
Applied tasks that combine environment and files and style in one piece of work.
- 6
Debugging
Debugging introduced and practised, completing the toolkit needed for the project.
- 7
Project build
Guided build session for the module project: Command-line productivity tool.
- 8
Test, present and reflect
Finish, test against the checklist, present the work and explain the decisions behind it.
Project lab
Command-line productivity tool
Every module ends with something the student built themselves and can demonstrate. This is the piece that goes into their portfolio and gets explained out loud at the end of session 8.
Try this at home
Build a command-line tool that accepts arguments, then run it from any folder on your computer. That is the moment it stops being homework.
It is finished when
- It works from start to finish without breaking
- You can explain every part of it in your own words
- You tested it and improved at least one thing afterwards
- Someone else used or understood it without your help
By the end of this module
Students finishing Module 1 can:
- Explain and use environment and files without prompting
- Explain and use style without prompting
- Explain and use debugging without prompting
- Build and finish command-line productivity tool
- Test your own work and correct what you find
- Talk an adult through what you made and why
Word bank
The vocabulary introduced here, in plain language:
- PEP 8
- The official Python style guide.
- CLI
- Command-line interface — a text-driven program.
- dependency
- External code a project needs to run.
Module challenge
Think you have got this?
0 XPLevel 1 · Curious Beginner
6 quick questions drawn from this module — vocabulary, the project you build, and a myth-or-fact round. Every wrong answer explains itself, so a mistake still teaches you something.
Your child's free trial is one message away.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.