A real use: summarising a web-server log
Five made-up log lines, each with a time, a request, a status code and how many milliseconds the reply took. Four small modules (datetime, statistics, collections, json) do the whole job in a few lines. line.split() cuts a line into words (Topic 3.2).
Python ships with hundreds of ready-made modules: maths, randomness, dates and time zones, the operating system, iteration tools, statistics and JSON. Knowing what exists, and how to read the documentation, saves you from rewriting what is already built, tested and fast.
Change the code and press Run (Ctrl+Enter). Predict what will happen first, then break it on purpose and read what changes. Your edits are saved and match the lesson page.
Ready for more? This phase has 5 hands-on exercises with automatic checks.
Practice questions
Write the code in the editor, run it, then open the model answer to compare.
Use statistics to print the mean and median of [4, 8, 15, 16, 23, 42].
Call random.seed(1), then print a list of three dice rolls made with random.randint(1, 6). Then explain in one sentence why running the program again gives the same three numbers.
Print how many days there are from date(2026, 10, 9) to date(2026, 12, 25) (subtract the earlier date from the later one and use .days).
Put the dictionary {"name": "Asha", "scores": [90, 85]} in a variable, then use json.dumps to print it with an indent of 2 and sorted keys.
Explain it without notes
What is the standard library, and how do you know a module belongs to it?
Why do tests and experiments call random.seed(...), and why not use random for passwords?
How should an application treat time zones?
How do you find out how to use a module you have never seen?
Expected output
first request at: 09:15:02
average time (ms): 305
median time (ms): 120
status counts: {'200': 3, '500': 1, '404': 1}
{"requests": 5, "slowest_ms": 910, "errors": 2}