Python Fundamentals

Structuring text-based programmes through variables, conditions, loops, collections, functions, files and error messages.

Completion evidence: Working Python programme, sample inputs, expected outputs and failure tests.

Write a small input-validating programme split into functions; test at least three valid and three invalid inputs.

The order is recommended. Before a project page, complete evidence from foundation, practice and debugging lessons.

Structuring text-based programmes through variables, conditions, loops, collections, functions, files and error messages. A correct example alone is therefore insufficient. Completion evidence should be working python programme, sample inputs, expected outputs and failure tests, tested with normal, boundary and invalid inputs.

In the first cycle, pair foundation and application among Getting Started with Files, Functions, For and While Loops, Your Setup and First Program, Reading Error Messages. Predict the result, run or measure it, then explain any difference. Even when prediction and reality match, state which changed condition would break the result.

In the second cycle, complete this laboratory: Write a small input-validating programme split into functions; test at least three valid and three invalid inputs. Do not close with one successful screenshot. Keep the input table, expected behaviour, actual behaviour, error or measurement and the correction in one file.

In the final cycle, connect Project: Simple Sports Statistics, Variables and Data Types, Conditions in Python, What Is Python and Where Is It Used?, Randomness and Simple Game Logic. Let one lesson's output become another lesson's input; show where safe stopping is needed when data type, unit, wiring, timing or user expectation changes.

Repeat the same task one month later with less source support. Compare not only speed or appearance but test coverage, explainability, safety and whether another person can rebuild the work.

Use the foundation produced in Getting Started with Files as an input to Modules and Libraries. Then show in Randomness and Simple Game Logic how the same idea changes under the limits of a larger system. This bridge carries the goal of structuring text-based programmes through variables, conditions, loops, collections, functions, files and error messages. beyond one isolated example.

Add three columns to the working python programme, sample inputs, expected outputs and failure tests file: knowledge carried from the previous lesson, condition changed in the new lesson and result observed in testing. Sharing a word does not establish a connection; one lesson’s output should genuinely become the next process’s input.

Test the connection through this laboratory: Write a small input-validating programme split into functions; test at least three valid and three invalid inputs. After the first attempt, add an edge condition such as empty data, wrong type, disconnected input, extreme value or user error. Record whether the system remains understandable and safe beyond the normal example.

• Name the previous lesson output
• State the one changed condition
• Separate expected and actual result
• Define safe stopping or error feedback
• Make one change in the second version