Python Fundamentals — Learning Environment

A structured, documentation-first curriculum for engineers who want to understand Python deeply — not just ship code. We build one real project, the Country Explorer, from a single dictionary through to a tested application calling a real API.

Overall Progress
Sessions completed 0 / 47
Complete: 0 Active: Session 1 Locked: 46
Active session: Session 01 — Hello, World & Variables  ·  Layer 0: Python Basics

Documentation Sections

Syllabus
All 47 sessions, layer breakdown, unlock gates, and dependency ordering.
Sessions
Individual lesson docs — objectives, quizzes, labs, and commit checkpoints.
Quizzes
Quiz bank and score tracker. Must score 80% to advance each layer.
Labs
Lab reference index. Step-by-step coding exercises per session.
Architecture
Architecture decision log. Every structural choice documented here.
Session Notes
Running notes from each session. Questions raised and answered.
Commit Reviews
Every commit reviewed here before moving forward. No skipping.
Prompt Log
Every prompt sent to the AI in this project, logged in order.

Curriculum Layers

Layer Topic Sessions Status Unlock Condition
0 Python Basics 01 – 04 Active None — starting point
1 Python Foundations 05 – 11 Locked Session 04 quiz ≥ 80%
2 Object-Oriented Basics 12 – 19 Locked Session 11 quiz ≥ 80%
3 State & Interactivity 20 – 26 Locked Session 19 quiz ≥ 80%
4 Mock Data 27 – 30 Locked Session 26 quiz ≥ 80%
5 Testing 31 – 35 Locked Session 30 quiz ≥ 80%
6 Architecture 36 – 40 Locked Session 35 quiz ≥ 80%
7 Real World 41 – 44 Locked Session 40 quiz ≥ 80%
8 Beyond the Fundamentals 45 – 47 Locked Session 44 quiz ≥ 80% (optional — Layer 7 is the core curriculum's natural end point)

Rules We Follow

  1. Never jump ahead — concepts taught in strict dependency order.
  2. One session = one tiny slice = one commit.
  3. Never teach a Python feature without connecting it to why it matters for the project.
  4. Never build large features in one session.
  5. Every coding session ends with documentation updates.
  6. We must understand every commit before proceeding.
  7. Score below 80% on a quiz = repeat the lesson.
  8. Always use fake/mock data before real APIs.
  9. Do not optimize for cleverness over readability.
  10. Code must stay beginner-readable.
  11. Never hide complexity behind abstractions too early.
  12. Force review of every changed file.
  13. Every lesson completable in 35–40 minutes.

Package manager: pip  ·  Testing: pytest  ·  Language: Python 3  ·  Project: Country Explorer