Class vs Instance: The Blueprint Behind Every Object

What two design decisions turn a real-world thing into a Python type — and why is a car's blueprint never the only right one?

Finger exercises

Short drills on what this video just taught. Write the code, run the checks, and reveal the answer only if you are stuck.

0 / 5 passed

Exercise 1 of 5

Six values, six types

Every object carries a type, and the type is what decides which operations the object will accept. Work out, in your head, the type of each of these six expressions:

7 / 2
7 // 2
"7"
[7, 7]
(7, 7)
{7: "seven"}

Assign to value_types a list of those six types, in that order. Write the types themselves — int, not the string "int".

# Exercise 1: the type of each of the six expressions, in order.
value_types = []  # your code here — six types, in order

# Exercise 1: the type of each of the six expressions, in order.
value_types = []  # your code here — six types, in order

Python runs in your browser

⌘/Ctrl + Enter runs

is a list with six entries

every entry is a type, not a string or a sample value

each expression is paired with its own type

←Previous deep_rev: One Type Test Reverses Every Layer Next Choosing Data and Behavior: Elevators, Employees, and Stacks →