DoAssignment study guide

A4.3 · Interpret programming-tool error messages

Learn to interpret programming-tool error messages through clear examples and targeted practice.

Ontario Grade 11 Computer Science

Programming Concepts and Skills

ICS3U study topic A4.3: Use the message as a clue to locate and understand a programming error.

When a program does not work, a programming tool may show an error message. The message is not a complete solution: it is evidence about what the tool could not understand or do. Interpreting it means reading the useful parts, checking the indicated code, and explaining the problem in plain language. This lesson uses Python 3 examples. A classroom may use a different programming language or tool, so its wording and line numbers may differ. The code here is displayed for study and is not claimed to have been run.

What you will learn

Identify the main clue in a programming-tool error message.
Use a reported error type and source line to inspect the relevant code.
Explain what a simple error means and make a focused correction.
Distinguish an error message from the program's expected output.

What an error message tells you

A programming tool checks or runs code and may report a problem. Depending on the tool and the problem, its message can name an error type, show a line number, point to a location in that line, or describe an operation that could not be completed. These parts help you decide what to inspect.

Read the message from the main clue to the code: identify the error name or description, find the indicated line, then compare that line with the surrounding statements and the values or names they use. A line number is a useful starting point, not proof that every mistake is located exactly there. For example, a missing character on one line can make the next line difficult for the tool to interpret.

The goal is to explain the message, not to guess a repair from the error name alone. Check what the code is trying to do and whether the message fits that specific situation. After a focused correction, use the classroom's normal process to check the code again; do not assume a correction has been verified until it has been checked.

Look for the error name or description first.
Use the reported line or location as a clue, then inspect nearby code.
Explain the problem in terms of the code, not just by repeating the error label.

A practical reading routine

Use this routine when a tool presents an error. First, read the full message rather than stopping at its first line. Next, find the named type of error or the specific description, and locate the line it points to. Then inspect the relevant names, punctuation, and operation in context. Ask what the program was trying to do at that point and why that action could not succeed.

For example, if a message says a name is not defined, check whether that name was created earlier and whether its spelling matches. If it says a value has an unsuitable type for an operation, check the values involved and whether that operation makes sense for them. If it reports a syntax problem, inspect the punctuation and structure around the indicated location. These are ways to investigate, not guarantees that every message will use identical wording.

For a short program, a useful input-process-output description keeps the investigation grounded. Identify any input, the operation the code attempts, and what output would follow if the code could complete. If the program stops with an error before reaching an output statement, do not report that output as if it occurred. You can still trace the intended state from the shown statements and describe the expected result after a clearly stated correction.

Read the whole message and connect it to a specific part of the code.
Check the spelling and prior creation of names when investigating a missing-name message.
Do not claim an output was produced when an error prevents the program from reaching it.

Careful corrections and communication

A good correction addresses the cause indicated by the code and message. Change only what is needed to make the statement match the program's intention. Then explain both parts: what the message indicates and why the correction addresses it. If several changes are made at once, it becomes harder to tell which change mattered.

Error messages can be unfamiliar, and different programming tools can describe similar problems in different ways. Treat the message as evidence to interpret, not as a verdict about the programmer. In class, include the language and tool when reporting an issue, quote the relevant message accurately, and show the small code area needed to understand it.

A message may identify a problem that appears before the line where the tool points. If the indicated line seems valid, inspect the preceding statement and its punctuation as well. This is especially useful for syntax messages, where the tool may only recognize that the code cannot be read correctly once it reaches a later location.

Make a focused correction tied to the evidence.
A reported line is a clue; nearby earlier code may also matter.
Describe the error without treating it as a personal failure.

From message to explanation

The examples below use Python 3 syntax and familiar error-message forms. Exact wording, punctuation, and line-number display can vary with the tool or version, so focus on the error type and what the code is doing. The examples show how to reason from a message; they do not represent code that was executed.

In each example, separate the code as written from the corrected version and its expected result. The original code's error means it does not complete normally. An expected result is therefore derived by tracing the corrected code, not presented as actual output from the faulty code.

Keep the original error, the explanation, and the corrected trace distinct.
Derive expected results from the shown statements rather than claiming execution.

NameError example: trace of the focused correction

Point in code	Name or action	State or expected result
Assignment	points = 8	points contains 8
Faulty reference	score	No earlier assignment creates score
Corrected display	print(points)	Expected displayed value: 8

Worked example

A name that has not been created

A learner is given the message NameError: name 'score' is not defined, pointing to the line that tries to display score. Explain the clue, identify the cause in the code, and state the intended result after correcting the name.

Python 3

points = 8
print(score)

# Focused correction:
print(points)

Read the clue
NameError indicates that Python 3 reached a name it could not find among the names created for the program. The message specifically names score, so inspect that spelling and look for an earlier assignment.
Compare the code
The assignment creates points, but the display statement asks for score. Those are different names. The error is not saying that the number 8 cannot be displayed; it is saying that score was not created in this code.
Trace the focused correction
Change the display statement to use points. The input is the value assigned in the code, 8. After the assignment, points contains 8; the corrected display statement refers to that same name, so the expected displayed value is 8.

Answer: The message means score has not been defined. The code creates points, so using points consistently corrects the name mismatch. The corrected code is expected to display 8.

Check: The expected display value follows from the assignment to points and the corrected reference. The faulty code does not successfully display score.

Worked example

An operation uses incompatible values

A tool reports TypeError for a statement that adds a number to text. Interpret the message and decide how to change the statement if the intention is to display a greeting followed by the number 3.

Python 3

count = 3
print("Visitors: " + count)

# Focused correction:
print("Visitors: " + str(count))

Connect the type to the operation
TypeError indicates that an operation was attempted with values that are not suitable for that operation. Here, the plus sign is being used between text and the number 3. The message directs attention to that combination.
Choose a correction that fits the intention
The intention is to display the greeting followed by the number. Converting the number to text makes both parts text, so the plus sign can join them. In Python 3, str(3) produces the text '3'.
Trace the expected result
The input is the literal number 3 and the text 'Visitors: '. The corrected expression joins that text with the text form of 3. The expected displayed line is Visitors: 3. This is a trace of the corrected code, not a report that the code was run.

Answer: The message indicates that the plus operation is being used between text and a number. Convert the number to text before joining it to the greeting; the corrected code is expected to display Visitors: 3.

Check: The corrected expression joins two text values. The original expression combines text and a number without converting either value.

Worked example

A syntax message near a missing colon

A Python 3 tool reports SyntaxError while showing a line that begins with if ready. Interpret why the tool cannot read the code and state the expected output after the indicated punctuation is added.

Python 3

ready = True
if ready
    print("Done")

# Focused correction:
if ready:
    print("Done")

Interpret the message
SyntaxError means the tool cannot read the code's structure as written. In Python 3, an if statement's condition line needs a colon before the indented statement. Inspect the shown line and its nearby structure for that missing punctuation.
Check the condition and correction
The variable ready is True, so the condition is satisfied. Adding a colon after the condition gives the if statement the required punctuation. The indented print statement is then the statement controlled by that condition.
Trace the corrected code
The code assigns True to ready. The condition is therefore true, so the indented statement displays Done. This is the expected result after the syntax correction; the original code cannot be traced as a normally completed program because it has a syntax error.

Answer: The SyntaxError points to code that is not written in a form Python 3 can read. The if line is missing its colon. After adding it, ready is True, so the expected output is Done.

Check: The colon completes the if statement's condition line. The true condition allows the indented display statement to be reached.

Common mistakes and how to avoid them

Treating the reported line number as proof that the entire problem must be on that line.

Correction: Use the line as a starting clue and inspect nearby code, especially the statement just before it.

Repeating an error name without explaining how it relates to the code.

Correction: Name the specific name, value, operation, or punctuation that the message helps you inspect.

Reporting the expected output of faulty code as though the tool produced it.

Correction: Say that the original code stops with an error, then label any output as the expected result after a stated correction.

Changing several unrelated parts of a program at once.

Correction: Make a focused change that addresses the evidence in the message, then check the code using the classroom's normal process.

Lesson summary

An error message gives clues about what a programming tool could not understand or do.
Read the error description, find the reported location, and connect it to the code's names, values, operation, or punctuation.
A line number is a starting point; nearby code may also explain the problem.
Explain a focused correction and trace any expected result without claiming the program was run.

Check your understanding

Question 1

A Python 3 message says NameError: name 'total' is not defined on a display line. The code earlier assigns a value to points, not total. What is the best interpretation?

The name total has not been created in the shown code; check whether the display should use points.
The number assigned to points is too large to display.
The tool has confirmed that the output is the word total.
correctIndex": 0, "explanation":"NameError identifies a name the code cannot find. Comparing the assignment and the display line reveals the possible name mismatch; the message does not report an output."

Show answer and explanation

The name total has not been created in the shown code; check whether the display should use points.

NameError identifies a name the code cannot find. Comparing the assignment and the display line reveals the possible name mismatch; the message does not report an output.

Question 2

A tool reports SyntaxError on an if statement. What should you do first?

Inspect the statement's structure and nearby punctuation, using the message location as a clue.
Assume the condition is false and report the code's output.
Change every variable name in the program.
correctIndex": 0, "explanation":"A syntax message means the tool cannot read the code structure as written. Inspecting the indicated and nearby code is a focused first step."

Show answer and explanation

Inspect the statement's structure and nearby punctuation, using the message location as a clue.

A syntax message means the tool cannot read the code structure as written. Inspecting the indicated and nearby code is a focused first step.

Question 3

A faulty statement combines text and a number and produces a TypeError. The goal is to join them as text. Which explanation is best?

The operation uses values of incompatible types; convert the number to text before joining.
The error means the tool has already displayed the joined text.
The message proves that all numbers must be removed from the program.
correctIndex": 0, "explanation":"TypeError points to an operation that is unsuitable for the given value types. Converting the number to text makes the values compatible with joining as text."

Show answer and explanation

The operation uses values of incompatible types; convert the number to text before joining.

TypeError points to an operation that is unsuitable for the given value types. Converting the number to text makes the values compatible with joining as text.

Key terms

Error message: Text from a programming tool that describes a problem encountered while reading or working with code.
NameError: A Python error indicating that a name used in the code cannot be found as a name created for the program.
TypeError: A Python error indicating that an operation was attempted with values of unsuitable types.
SyntaxError: A Python error indicating that the code's structure cannot be read as written.

Continue through ICS3U

View the complete ICS3U Ontario Grade 11 Computer Science curriculum and lessons

About this lesson and its review

Published by DoAssignment. This reviewed lesson follows Ontario Grade 11 Computer Science (ICS3U), expectation A4.3. It is a study resource, not an official curriculum publication.

Before publication, content is checked for structure, mathematical or chemical notation, calculations, course boundaries, and readability. Errors can still occur, so corrections are welcomed.

Official curriculum reference

Report a correction or ask a question