YOUR CHALLENGE ROUTE

Complete these tasks in your Python editor. The page is a challenge guide, not a general Python runner. Use fictional details where helpful. Work in order or choose a task matching an area you need to practise.

The core solutions use Section 1 skills only. They state valid-input assumptions instead of introducing unexplained if statements, loops or exception handling. Observe and record those limitations when testing.

TRACK YOUR TESTED SOLUTIONS

Tick a task only after you have run it, checked at least two relevant cases and explained one line. These are self-recorded checks, not an automatic assessment of your source code.

Progress lasts while this page is open. Save your actual Python files in your project folder.

01 | FOUNDATION

PROVE YOUR SETUP

Create a file that proves you can edit, save, run and reopen a Python program. Choose IDLE or VS Code with the Microsoft Python extension.

YOUR REQUIREMENTS

• Save setup_check.py in your Section 1 folder.
• Print three separate lines: a title, an invented first name and a short coding goal.
• Change the goal, save and run the whole file again.
• Close the editor, reopen the saved file and rerun it.

TEST YOUR PROGRAM

print("Python setup check")
print("Name: Maya")
print("Goal: build a robot controller")

Extension: Show a partner the source and output. Explain which window accepts code and where the program’s output appears.

Revisit the related lesson

02 | FOUNDATION

DESIGN A CONSOLE TICKET

Create a ticket for a fictional coding event. The output should communicate clearly, rather than look like unrelated values.

YOUR REQUIREMENTS

• Print the event title and a blank output line.
• Print a labelled attendee count calculated from 4 + 6.
• Print a closing message.
• Add a useful # comment explaining a purpose.

TEST YOUR PROGRAM

# Show a readable event ticket
print("Coding Club Open Day")
print()
print("Expected attendees:", 4 + 6)
print("Bring your curiosity!")

Extension: Add a second labelled calculation for equipment needed. Explain why its answer is meaningful.

Revisit the related lesson

03 | REPAIR

REPAIR THE WELCOME PROGRAM

The broken source below is intended to greet the user and display the numeric total 15. Find each issue rather than replacing it without explanation.

YOUR REQUIREMENTS

• Correct the name and paired punctuation.
• Make the total a numeric calculation.
• Keep the useful comment unprinted.
• Explain each correction in your exercise book.

SOURCE TO REPAIR

# Welcome a new coder
Print("Welcome to Python)
print("Total:", "12 + 3"

TEST YOUR PROGRAM

# Welcome a new coder
print("Welcome to Python")
print("Total:", 12 + 3)

Extension: Add a line containing an apostrophe, choosing quotation marks that keep the string valid.

Revisit the related lesson

04 | FOUNDATION

BUILD A TYPED PROFILE

Create a fictional learner profile using the four basic Python types introduced in Section 1.

YOUR REQUIREMENTS

• Store a name and code 0072 as strings.
• Store a whole-number project count as int.
• Store fractional practice hours as float.
• Store a completion flag as bool.
• Print a readable report and use type() to inspect each kind.

TEST YOUR PROGRAM

username = "Maya"
student_code = "0072"
projects = 3
practice_hours = 2.5
finished = False
print(f"{username} ({student_code}) completed {projects} projects.")
print(f"Practice: {practice_hours} hours; finished: {finished}")
print(type(username), type(projects), type(practice_hours), type(finished))

Extension: Rename one vague identifier in your own solution. Explain how the new name improves readability.

Revisit the related lesson

05 | TRACE AND BUILD

TRACE A SCORE UPDATE

Predict the values of score and saved_score, then write a program that proves your prediction.

YOUR REQUIREMENTS

• Start score at 10.
• Copy its current numeric value into saved_score.
• Add 5 to score using score = score + 5.
• Print both names with labels.
• Explain why the saved value does not change.

TEST YOUR PROGRAM

score = 10
saved_score = score
score = score + 5
print("Current score:", score)
print("Saved score:", saved_score)

Extension: Add another update of seven after the first. Predict both final values before running again.

Revisit the related lesson

06 | APPLY INPUT

CALCULATE TRIP DISTANCE

Ask a traveller for a first name, a whole-number trip duration and a daily distance. Report the total planned distance.

YOUR REQUIREMENTS

• Use input() for the name and strip surrounding whitespace.
• Convert the day count using int().
• Convert daily kilometres using float().
• Multiply days by daily distance.
• Print a personalised result with kilometres as the unit.

TEST YOUR PROGRAM

username = input("First name: ").strip()
days = int(input("Trip days (whole number, 0 or more): "))
daily_km = float(input("Daily distance in kilometres: "))
total_km = days * daily_km
print(f"{username}, your planned distance is {total_km:.1f} km.")

Extension: Add a separate whole-number rest-day input. Calculate active days from the stated valid-input assumptions, then test a trip with one rest day.

Revisit the related lesson

07 | REPAIR INPUT

REPAIR TEXT ADDITION

A student asks for two numbers but receives the output 123 when entering 12 and 3. Diagnose the problem and correct it.

YOUR REQUIREMENTS

• Explain the original output before changing the source.
• Convert both responses to numbers.
• Allow fractional values in the corrected program.
• Print a labelled numeric sum.

SOURCE TO REPAIR

first = input("First number: ")
second = input("Second number: ")
print(first + second)

TEST YOUR PROGRAM

first = float(input("First number: "))
second = float(input("Second number: "))
print("Sum:", first + second)

Extension: Create a separate whole-number version using int and explain what happens for response 2.5.

Revisit the related lesson

08 | REPAIR A FORMULA

FIND THE CORRECT MEAN

The expression first + second / 2 runs, but it does not normally calculate the mean of both numbers. Repair the formula and prove it with test cases.

YOUR REQUIREMENTS

• Store first and second as numeric values.
• Group their whole sum before dividing by 2.
• Print the mean with a label.
• Compare the original and repaired results for 8 and 12.

TEST YOUR PROGRAM

first = 8
second = 12
mean = (first + second) / 2
print("Mean:", mean)
print("Original formula:", first + second / 2)

Extension: Extend to three named values and calculate their mean. Use values 3, 6 and 9 to check for a result of 6.0.

Revisit the related lesson

09 | APPLY ARITHMETIC

GROUP COMPONENTS INTO KITS

A robotics club groups identical components into equal-size kits. Report complete kits and leftover components.

YOUR REQUIREMENTS

• Receive a non-negative whole-number component count.
• Receive a positive whole-number kit size.
• Use // for complete kits and % for leftovers.
• Label both results.
• Check that complete kits × kit size + leftovers reconstructs the input.

TEST YOUR PROGRAM

components = int(input("Components (whole number, 0 or more): "))
kit_size = int(input("Components per kit (whole number greater than 0): "))
complete_kits = components // kit_size
leftovers = components % kit_size
print("Complete kits:", complete_kits)
print("Leftover components:", leftovers)
print("Check total:", complete_kits * kit_size + leftovers)

Extension: Add a true-division report for the ratio components / kit_size and explain why it differs from complete kits.

Revisit the related lesson

10 | STRETCH THE BASICS

MAKE A MEASUREMENT REPORT

Create a square-planning tool that calculates area and perimeter from a side length in centimetres.

YOUR REQUIREMENTS

• Read a non-negative numeric side length using float().
• Use ** 2 for square area.
• Use 4 * side for perimeter.
• Display area in square centimetres and perimeter in centimetres.
• Format both values to two decimal places.

TEST YOUR PROGRAM

side = float(input("Square side length in centimetres: "))
area = side ** 2
perimeter = 4 * side
print(f"Area: {area:.2f} square cm")
print(f"Perimeter: {perimeter:.2f} cm")

Extension: Add a named price_per_square_cm value and estimate material cost from area. State that this is a beginner estimate rather than exact financial accounting.

Revisit the related lesson

11 | CAPSTONE

BUILD A PERSONALISED PRACTICE PLANNER

Build your own version of the Section 1 calculator project. Choose a theme such as coding, robotics or music practice.

YOUR REQUIREMENTS

• Greet a user by first name.
• Calculate completed practice from sessions, session minutes and extra minutes.
• Convert total minutes to hours.
• Calculate average minutes per positive completed-project count.
• Plan a separate future whole-hour block using a positive whole-minute session size.
• Report complete future sessions and leftover target minutes.
• Use comments, meaningful names and a named minutes-per-hour constant.

TEST YOUR PROGRAM

# Personalised practice calculator
# Core version assumes valid numbers and positive divisors.
MINUTES_PER_HOUR = 60

print("Practice planner")
username = input("First name: ").strip()
sessions = int(input("Completed sessions (whole number, 0 or more): "))
minutes_per_session = float(input("Minutes per completed session: "))
extra_minutes = float(input("Extra practice minutes: "))
projects = int(input("Completed projects (whole number greater than 0): "))
target_hours = int(input("Future target hours (whole number, 0 or more): "))
planned_minutes = int(input("Future session minutes (whole number greater than 0): "))

# Completed practice and mean allocation per project
total_minutes = sessions * minutes_per_session + extra_minutes
total_hours = total_minutes / MINUTES_PER_HOUR
average_minutes = total_minutes / projects

# A separate future practice block
target_minutes = target_hours * MINUTES_PER_HOUR
complete_sessions = target_minutes // planned_minutes
leftover_minutes = target_minutes % planned_minutes

print()
print(f"Practice report for {username}")
print(f"Completed practice: {total_minutes:.1f} minutes")
print(f"Completed practice: {total_hours:.2f} hours")
print(f"Average practice per project: {average_minutes:.1f} minutes")
print(f"Future target block: {target_minutes} minutes")
print(f"Complete future sessions: {complete_sessions}")
print(f"Unused time in that block: {leftover_minutes} minutes")

Extension: Add a minutes-to-seconds report, then rerun the known tests to check that your change has not altered earlier results.

Revisit the related lesson

12 | REFLECT AND EXTEND

TEST, IMPROVE AND HAND OVER

Improve one of your completed programs and let a partner use it without verbal instructions. Provide evidence that the improvement works.

YOUR REQUIREMENTS

• Write a short user guide with valid sample input and units.
• Record at least three expected and actual results.
• Include an exact-division or zero-quantity case where suitable.
• Document invalid text and zero-divisor limitations where relevant.
• Add one useful calculation and repeat the earlier tests.
• Explain one code design choice using because or therefore.

TEST YOUR PROGRAM

# A useful extension to the completed-practice calculation
MINUTES_PER_HOUR = 60
SECONDS_PER_MINUTE = 60
sessions = 3
minutes_per_session = 25.0
extra_minutes = 10.0
total_minutes = sessions * minutes_per_session + extra_minutes
total_seconds = total_minutes * SECONDS_PER_MINUTE
print(f"Completed minutes: {total_minutes:.1f}")
print(f"Completed seconds: {total_seconds:.0f}")

Extension: List the next improvements you would make with comparisons, decisions and loops. Describe their purpose without using syntax you have not learned yet.

Revisit the related lesson

KEEP A SMALL TEST RECORD

For each test, write the input, predicted output, actual output and whether they match. If a mismatch occurs, identify whether it came from conversion, a formula, the chosen operator, units or displayed wording.

For a known limitation, state the observed exception and the assumption it breaks. Do not mark an error as a successful robust response just because the current version was expected to fail.

READY FOR THE NEXT SECTION?

You are ready to move on when you can save and run a file, explain text versus numbers, collect and convert suitable input, choose arithmetic operators and test a result you predicted.

If one skill is uncertain, revisit its lesson and change a worked example before repeating the challenge. The Section 1 workbook is coming soon.