Loading...
CodeCraft Juniors
Python Programming · Day 36 of 40

Errors, Debugging & try/except

Read error messages, locate bugs and prevent common input crashes.

60 minutesLive + guided practiceBeginner friendly
01 · LEARNING TARGETS

What students should understand today

  • Syntax Vs Runtime ErrorsUnderstand what it means, where it is used and practise it in a small example.
  • TracebacksUnderstand what it means, where it is used and practise it in a small example.
  • Try/ExceptUnderstand what it means, where it is used and practise it in a small example.
  • Defensive InputUnderstand what it means, where it is used and practise it in a small example.
02 · TEACHING NOTES

Core lesson

Start with the idea, not the syntax. Read error messages, locate bugs and prevent common input crashes. The instructor should connect the topic to something students already understand, then introduce the exact terms they need for today.

Build in small steps. The teacher first models one example, then students rebuild the same idea with different values so they learn the logic rather than memorising one answer. Pause after each important change and ask students to predict what will happen before running or refreshing the result.

Develop good habits. Students should type the code themselves, run it frequently and read any error message before changing the code. Keep naming, indentation/structure and output clear enough that another student could follow the work.

03 · LIVE BUILD

Fix syntax/runtime bugs and wrap numeric input with try/except.

1

Plan the result first: decide what the user/student should see or be able to do at the end.

2

Build the smallest working version using today’s main concepts and test it immediately.

3

Add one improvement at a time and ask students to explain why each line/element is needed.

4

Test with at least two different inputs, screen sizes or scenarios and fix one issue together.

04 · STUDENT CHALLENGE

Independent practice

Debug a broken mini program, then add one friendly error message.

Teacher rule: give hints in steps, but avoid typing the complete answer for the student. The goal is to make them think, try and correct.
05 · END-OF-DAY CHECK

Before moving to the next day

  • I can explain syntax vs runtime errors in simple words.
  • I can explain tracebacks in simple words.
  • I can explain try/except in simple words.
  • I can complete today’s mini task with only small hints.
Optional 10–15 minute home practice

Rebuild today’s example once without looking at the finished version. Change the names, values, text or design so the result is clearly your own.

← Day 35Day 37 →