Traceback (most recent call last):
  File "my_code.py", line 32, in <module>
    45 + "NameError"
TypeError: unsupported operand type(s) for +: 'int' and 'str'

Select one answer, then check.

• TypeError
  Correct. The last line of the traceback always names the error type: TypeError: unsupported operand type(s) for +: 'int' and 'str'.
• NameError
  Not quite. "NameError" here is just a string being added to 45 — it's not an actual error. The real error type is named on the last line.
• SyntaxError
  Not quite. Nothing here breaks Python's grammar; the code is valid, it just fails when run.
• No error occurred
  Not quite. A traceback like this one is only shown when an error did occur.
• We cannot tell the type of error from the information provided
  Not quite. The error type is always named on the last line of the traceback.

When your program has an error, the first thing you should do is:

Select one answer, then check.

• Check the error message and consider its meaning.
  Correct. Read and think about what the message is telling you before anything else — it often already points at the mistake.
• Ask for help.
  Not the first step. Asking for help is useful, but read the message yourself first — it often already answers your question.
• Curl up into a ball and cry.
  Understandable, but it won't fix the bug! Reading the error message will.
• Start debugging your program.
  Not the first step. Debugging comes after you understand what the error message is telling you.