Tuples

data-structures
beginner
Use immutable ordered records and unpack their values clearly.
  • Level: Beginner
  • Estimated time: 35–50 minutes
  • You will learn: Use immutable ordered records and unpack their values clearly.
  • Practice in: Google Colab, Jupyter, or VS Code

Questions

  • What problem does Tuples help us solve in a small Python program?
  • What should we predict before running the example?
  • What value, output, or error should we inspect after changing one line?

Objectives

  • Run a complete example for tuples in Colab.
  • Explain the example line by line using plain language.
  • Change one part of the code and predict the result before running it.
  • Recognize one common mistake and use the error message as evidence.

Hands-on episode: Tuples

A tuple is an ordered collection like a list, but it is immutable: you cannot replace an item inside it after creation.

We will learn this by running code, not by memorizing a definition first. Open the Colab notebook from the button above, find this section, and run each cell in order. Keep a small note beside the notebook with three columns: prediction, actual result, and what changed.

Example 1.1

Predict what each name receives when the tuple is unpacked.

point = (3, 5)
x, y = point
print(x)
print(y)

Run the cell once without editing it. If the result is different from your prediction, leave the prediction visible and write one sentence about the difference. That sentence is more useful than a perfect first guess.

Explain Example 1.1

  • point = (3, 5) creates one tuple with two positions.
  • x, y = point unpacks position 0 into x and position 1 into y.
  • The two print calls display the separate names after unpacking.

Now explain the example out loud or in a Markdown cell. Use short sentences: “this line creates…”, “this name stores…”, “this output appears because…”. If you cannot explain a line yet, run only the lines above it and inspect the values that exist at that moment.

Challenge 1.1

NoteChallenge

Try point[0] = 10. Python raises a TypeError because tuples do not allow item assignment. That is useful when you want a small record to keep its shape.

Show a safe way to approach the challenge
  1. Copy Example 1.1 into a new Colab cell.
  2. Change exactly one value, name, condition, or line.
  3. Write the expected output before running the cell.
  4. Run the cell and compare the actual result with your prediction.
  5. If the result surprises you, undo the change and try a smaller one.

Suggested first move: Try point[0] = 10.

Debugging checkpoint 1.1

WarningDebugging checkpoint

A one-item tuple needs a comma: single = (42,). Without the comma, (42) is just the number 42 in parentheses. If a tuple unpacking line fails, count the values on the right and the names on the left.

Do not debug by rewriting the whole example. Read the error type or surprising output, inspect the closest value with print(...) or type(...), then change one thing. This is the same routine you will use in larger projects.

Apply it

Represent a date as (year, month, day), unpack it into three names, and print a sentence. Then try to modify the month and read the error carefully.

Finish by adding a Markdown cell that answers: What did this example teach me that I can reuse in a project?

Key points

  • Learn the concept by running a complete, small example first.
  • Predict before execution so your thinking becomes visible.
  • Change one thing at a time so cause and effect stay clear.
  • Treat errors as clues about the exact line or value Python could not handle.

Why this matters

Use immutable ordered records and unpack their values clearly.

This lesson combines related subtopics that belong together in one learning conversation. You will still pause for a quiz after each section, but you do not need to jump between separate pages while building one clear explanation.

NoteGuiding questions

By the end of this lesson, you should be able to answer:

  • How do the sections in Tuples fit together?
  • Which small example demonstrates each section?
  • Which debugging clue should I check first for each section?
NoteLearning objectives

You will practice how to:

  • explain the shared concept for this lesson;
  • use each section as one step in a larger workflow;
  • complete 2 short section quizzes before moving on;
  • connect examples, mistakes, and debugging routines.

Lesson map

  • 1. Tuples — Store ordered records that should not be changed after creation.
  • 2. Tuple Unpacking — Assign multiple names from a tuple or sequence in one clear line.

1. Tuples

Store ordered records that should not be changed after creation.

TipAnalogy

A tuple is like a sealed envelope containing related pieces of information; you can read it but not rewrite it in place.

What this means

A tuple is an immutable ordered container often used for small fixed records.

Example 1

Predict what will happen before you run the code.

point = (3, 4)
print(point[0])
print(point[1])

Step-by-step explanation

  1. point = (3, 4) — pause here and say what this line reads, creates, changes, or displays.
  2. print(point[0]) — pause here and say what this line reads, creates, changes, or displays.
  3. print(point[1]) — pause here and say what this line reads, creates, changes, or displays.

After running the example, compare the actual output with your prediction. If they differ, do not erase your prediction. The difference is the part that can teach you the most.

Challenge

NotePractice

Change one input value, predict the new output, run the code, and explain the difference in one sentence.

Show one possible solution path
  1. Copy Example 1 into Colab, Jupyter, or a .py file.
  2. Mark the line you plan to change.
  3. Write a one-sentence prediction.
  4. Run the changed code.
  5. If the result surprises you, restore the original and change a smaller part.

The goal is not to find the only correct answer. The goal is to create a small experiment where you can explain cause and effect.

Common mistakes

WarningCommon mistake

Parentheses are common, but the comma creates a one-item tuple: single = (5,).

When you get stuck, use this debugging routine:

  1. Read the last line of the error message or inspect the unexpected output.
  2. Find the smallest line of code that could be responsible.
  3. Print or inspect the value and type at that point.
  4. Change one thing.
  5. Run again and record what changed.

Check your understanding

This quiz checks the ideas in this section before you move on.

2. Tuple Unpacking

Assign multiple names from a tuple or sequence in one clear line.

TipAnalogy

Unpacking is like handing out labeled seats: the first value goes to the first name, the second to the second name.

What this means

Unpacking matches positions on the right with names on the left.

Example 2

Predict what will happen before you run the code.

point = (3, 4)
x, y = point
print(x + y)

Step-by-step explanation

  1. point = (3, 4) — pause here and say what this line reads, creates, changes, or displays.
  2. x, y = point — pause here and say what this line reads, creates, changes, or displays.
  3. print(x + y) — pause here and say what this line reads, creates, changes, or displays.

After running the example, compare the actual output with your prediction. If they differ, do not erase your prediction. The difference is the part that can teach you the most.

Challenge

NotePractice

Change one input value, predict the new output, run the code, and explain the difference in one sentence.

Show one possible solution path
  1. Copy Example 1 into Colab, Jupyter, or a .py file.
  2. Mark the line you plan to change.
  3. Write a one-sentence prediction.
  4. Run the changed code.
  5. If the result surprises you, restore the original and change a smaller part.

The goal is not to find the only correct answer. The goal is to create a small experiment where you can explain cause and effect.

Common mistakes

WarningCommon mistake

The number of names must match the number of values unless you use starred unpacking.

When you get stuck, use this debugging routine:

  1. Read the last line of the error message or inspect the unexpected output.
  2. Find the smallest line of code that could be responsible.
  3. Print or inspect the value and type at that point.
  4. Change one thing.
  5. Run again and record what changed.

Check your understanding

This quiz checks the ideas in this section before you move on.

Notebook and Colab practice

Open a blank notebook at https://colab.new. Use one section at a time: copy the Example 1, predict the result, run it, answer the section quiz, and then move to the next section. This is better than copying the entire page at once.

Instructor note

Teaching notes
  • Treat each section as a short teaching episode.
  • Pause for the section quiz before introducing the next section.
  • Ask learners to compare sections: what stayed the same, and what changed?
  • If time is short, teach the first two sections live and assign the rest as practice.

Key points

TipKey points
  • Tuples: A tuple is an immutable ordered container often used for small fixed records.
  • Tuple Unpacking: Unpacking matches positions on the right with names on the left.
  • Use the section quizzes as gates: review before moving on if a quiz feels uncertain.

References

  • Python data structures tutorial: https://docs.python.org/3/tutorial/datastructures.html
  • Built-in types: https://docs.python.org/3/library/stdtypes.html
  • Python Tutorial: https://docs.python.org/3/tutorial/
  • Quarto OJS documentation: https://quarto.org/docs/interactive/ojs/
  • ipywidgets documentation: https://ipywidgets.readthedocs.io/en/stable/
Back to top