Python SyntaxError: the file never started running

What this error means

A SyntaxError is not a bug in your logic — it is Python refusing to compile your file. The interpreter reads the whole module and turns it into bytecode before it executes a single statement, and the parser hit a sequence of tokens that no Python grammar rule allows.

That timing is the most useful thing to know about this error. Nothing ran: not the print on line 1, not the import, not the code above the reported line. If you expected some output before the crash and got none, the exception is almost certainly a SyntaxError (or its subclass IndentationError).

Since Python 3.10 the messages are far more specific than the old catch-all invalid syntax: you now get expected ':', '(' was never closed, and even Maybe you meant '==' or ':=' instead of '='?. Read the message first — in most cases it names the fix.

A real example

scores = [90, 85, 72]

if len(scores) > 0
    print(sum(scores) / len(scores))

  File "report.py", line 3
    if len(scores) > 0
                      ^
SyntaxError: expected ':'

Note what the traceback does not have: no Traceback (most recent call last) header and no call stack. There is no stack because no function ever ran. A SyntaxError report is just a file, a line, a caret and a message.

The causes behind almost every SyntaxError

• Missing colon. Every if, elif, else, for, while, def, class, try, except, with and match header ends in :.
• = where == belongs. if answer = 42: is an assignment inside a condition — Python 3.10+ even suggests == or the walrus :=.
• An unclosed bracket or quote. sum([1, 2, 3 swallows every following line until the parser gives up, which is why the reported line is often far below the real mistake.
• A missing comma between list, tuple or argument items — [1 2] reads as two expressions with nothing joining them.
• Python 2 habits. print "hi" and except Exception, e: are both syntax errors in Python 3.
• A keyword used as a name. class = "10B" or lambda = 3 — class, lambda, pass, from, is, in, global and friends are reserved.

Why the caret often points at the wrong line

The parser reports where it discovered the problem, not where you made it. An unclosed bracket keeps the expression open, so the first token that cannot possibly continue it — usually on the next line — gets the caret:

total = sum([10, 20, 30
print("total:", total)

  File "report.py", line 1
    total = sum([10, 20, 30
                ^
SyntaxError: '[' was never closed

The rule of thumb: when the flagged line looks perfectly fine, the real error is on the line (or lines) above it. Modern Python points back at the opening bracket for you; older versions just said invalid syntax on line 2.

How to debug it

1. Read the message, not just the error name — expected ':' and '(' was never closed each name the fix outright.
2. Look at the reported line and the line above it. Unclosed brackets, quotes and missing commas always report late.
3. Let the editor help: matching-bracket highlighting and syntax colouring expose an unterminated string instantly — the rest of the file turns string-coloured.
4. Comment out the suspect block and re-run. If the error moves, you have isolated the region; if it does not, the real problem is earlier.
5. Check the Python version mismatch if you copied the code: print without parentheses and except Exception, e are Python 2 syntax.

Fix it interactively

Each of these free problems is a one-token syntax bug you repair in the browser — no setup, instant feedback:

• Missing colon in a for loop easy
• Missing colon after a function definition easy
• Using = instead of == in a condition easy
• A wrong quote type breaks the string easy
• Wrong syntax for adding a dictionary key easy

Related errors

• IndentationError — a subclass of SyntaxError — the tokens are legal, the whitespace is not.
• NameError — the file parsed fine, but a name used at runtime was never defined.
• TypeError — the next thing you meet once the file finally compiles and runs.

Full catalogue of messages and fixes: the Python errors guide. For the search-and-narrow routine itself, read the Python debugging guide.