# EDU-PYT-201 — learner workbook

Course: Python Programming Lecturer Practice
Version: 1.0.0 | Public pilot | 1 November 2026

## Before starting

Record your interpreter/compiler or editor version, access needs and prior experience. Use fictional data. This file is a local workbook, not an LMS submission or grade record.

## Evidence map

| Outcome | Artifact | Module | Acceptance |
|---|---|---|---|
| LO-01 | Execution trace explaining aliasing and mutation | Module 1 | Module lab acceptance and capstone rubric |
| LO-02 | Validated function with boundary and exception cases | Module 2 | Module lab acceptance and capstone rubric |
| LO-03 | Temporary-file tests for a CSV importer | Module 3 | Module lab acceptance and capstone rubric |
| LO-04 | A microteaching portfolio with a tested Python learning task | Module 4 | Capstone rubric |

## Repeat for each module

- My prediction and its reasoning:
- Command or editorial action performed:
- Actual result and environment/source version:
- Difference from the expected result:
- Controlled defect and how it was detected:
- Correction and recheck:
- Evidence filename and private storage location:
- Assistance received and fresh transfer evidence:
- One teaching misconception and feedback response:

## Capstone brief

Teach a 20-minute lesson on a CSV score importer. Require learners to distinguish missing files, missing columns and invalid numeric values, test a boundary case and explain one aliasing bug. Submit runnable standard-library code, a test suite, an accessible trace diagram and a rubric that rewards reasoning as well as output.

## Self-review

Score each criterion 0–4: correctness (30%), role performance (25%), verification (20%), accessibility (15%), handover (10%). Weighted score = sum(weight × level / 4). Pilot threshold: 75/100, correctness and verification at least level 3, critical conditions resolved. An authorized assessor must confirm formal results.

Critical condition: Silently accepting invalid input, leaking real learner data or fabricating test evidence requires correction.

## Handover and cleanup

Confirm the assessor and approved private submission channel before sending evidence. Remove faulty release copies, temporary files and unnecessary personal information. Record unresolved issues, the next action and your review date.