Named Exception Handlers, else, finally, and raise

How do named except blocks give ValueError and ZeroDivisionError their own recoveries, and when do else and finally run?

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

One handler for every mistake

Two users answered the prompt Tell me a number:. The first typed "12"; the second typed "twelve". Both answers are sitting in responses.

Build results so it holds one entry per response, in order: that response converted with int(), or the string "bug in user input" if the conversion fails. Use a single catch-all except here — you are not naming exception types yet.

# One entry per response — the converted number, or the fallback message.
responses = ["12", "twelve"]
results = []
# your code here

# One entry per response — the converted number, or the fallback message.
responses = ["12", "twelve"]
results = []
# your code here

Python runs in your browser

⌘/Ctrl + Enter runs

is a list

has one entry per response

converts the response that converts

substitutes the fallback message for the one that fails

←Previous try and except: Catching an Exception Instead of Crashing Next raise ValueError and assert: Enforcing Your Docstring →