TypeError: tuple cannot be changed

What this problem practises

Tuples are immutable containers that may themselves hold mutable objects, and it is the comma — not the parentheses — that builds one. Any unpacking where the counts disagree raises ValueError.

This is a fix-the-bug problem: a short program is given in its broken state, and the task is to repair the code so it produces the required output. The interactive editor runs your fixed version in the browser and checks it for you — no setup, no local interpreter.

Difficulty: medium — expect to hold two interacting rules in your head at once, such as a boundary combined with a mutation.

The challenge

Tuples are immutable, so this program crashes with TypeError. Fix it (convert to a list and back) so it prints (65, 11, 28).

The code runs in PyDebug’s in-browser compiler. Open the problem, run the snippet, watch the exact error or output, and keep iterating until it is right. Signed-in solves count toward XP and your daily streak.

The snippet

The interactive editor pre-fills exactly this code, broken and ready to repair:

t = (8, 11, 28)
t[0] = 65
print(t)

More tuples problems

• ValueError: too many values to unpack easy
• Tuple unpacking easy
• ValueError: too many values to unpack easy

Keep going

• Python debugging guide — a systematic method for finding bugs like this one fast.
• Browse every tuples problem in this topic.
• Common Python errors and what they actually mean, plus the Python glossary for any term used on this page.