Getters, Setters and str: Why the Method Outlives the Attribute

Why does renaming one data attribute break every caller who reached for it directly, while the ones who went through `get_age()` never notice?

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

Teach a ticket to print itself

The Ticket class below stores a row and a seat letter, and its __str__ is empty. Give it a body so that a ticket prints as the word seat, a colon, the row, another colon, then the letter — a ticket in row 12 with letter B must display exactly seat:12:B.

Then build that very ticket, row 12 and letter B, and assign the object to ticket.

# Give __str__ a body, then build the ticket described above.
class Ticket(object):
    def __init__(self, row, letter):
        self.row = row
        self.letter = letter

    def __str__(self):
        ...  # your code here

ticket = ...  # your code here

# Give __str__ a body, then build the ticket described above.
class Ticket(object):
    def __init__(self, row, letter):
        self.row = row
        self.letter = letter

    def __str__(self):
        ...  # your code here

ticket = ...  # your code here

Python runs in your browser

⌘/Ctrl + Enter runs

is a Ticket object

prints as the word seat, the row and the letter joined by colons

reads the ticket it was handed rather than one fixed answer

←Previous Data and Procedural Attributes: Building the Animal Class Next Attribute Abuse From Outside, and a Dictionary of Animal Objects →

Getters, Setters and __str__: Why the Method Outlives the Attribute

Teach a ticket to print itself

Getters, Setters and __str__: Why the Method Outlives the Attribute

Teach a ticket to print itself

Getters, Setters and str: Why the Method Outlives the Attribute

Getters, Setters and str: Why the Method Outlives the Attribute