Article · By Prabhat Kumar
Use an error message and traceback to locate a failure, reproduce it, and test a focused correction.
An error message is not a verdict on your ability; it is a report from a program that could not complete an operation. In a traceback, the final line usually names the exception and gives a short explanation. Start there. A SyntaxError, TypeError, NameError, and IndexError suggest different categories of problems, but the surrounding context still matters.
A traceback can include library calls as well as your own files. Find the frame that points to the line you wrote, then inspect that line and the values it uses. The marked line is where the error became visible, not always where the original mistake began. A variable may have been assigned incorrectly several steps earlier.
Record the input and the steps that cause the error. Then reduce the example while keeping the failure. A smaller reproduction removes unrelated code and makes it easier to test a hypothesis. If the error appears only with one input, compare that input with a case that works and identify the meaningful difference.
Ask what type and value the program had at the failing line. Is text being used as a number? Is an expected key missing? Is an index outside a collection? Temporary logging or a debugger can expose those facts. Check the language's rules and documentation when the behavior is unclear instead of making several speculative edits at once.
After forming a specific explanation, change the smallest relevant part and rerun the same failing case. Then test a normal case and a boundary case so the fix does not merely hide the original error. If a new exception appears, read it as new evidence. Keep the test or minimal reproduction when it can prevent the same issue from returning.
When you need help, include the exact error text, the smallest relevant code, what you expected, what happened, and the steps to reproduce it. Remove passwords, tokens, personal records, and other private data first. A clear question helps another person reason about the problem without guessing or asking you to repeat basic context.
Once the issue is solved, write down the cause in a sentence and add a test when the behavior matters. A useful note is specific: for example, a conversion failed because a form value remained text. Avoid recording secrets or personal input in logs. This small review turns an interruption into a reference you can use the next time a similar exception appears.
text = 'twenty'
try:
number = int(text)
except ValueError as error:
print(type(error).__name__)
print('The text is not a whole number.')ValueError
The text is not a whole number.