Quick Fixes for Python EOL While Scanning String Literal

SyntaxError: EOL while scanning string literal means Python reached the end of a line while still inside a string. A quote was opened and never closed. Newer Python versions phrase it as unterminated string literal, which is clearer, but the cause is identical. There are five ways to get there and each has a distinct fix.

Cause 1: a missing closing quote#

name = "Ana

SyntaxError: EOL while scanning string literal

The obvious one. In an editor with syntax highlighting, everything after the opening quote turns string-coloured and stays that way, which makes it easy to spot once you know to look.

Cause 2: mismatched quote characters#

message = "Hello there'

Opened with a double quote, closed with a single. Python is still waiting for the matching double quote when the line ends. Pick one style and be consistent — most Python code uses double quotes by default.

Cause 3: an apostrophe inside single quotes#

text = 'It's a fine day'

The string ends at the apostrophe in “It’s”, and then s a fine day' is nonsense to the parser. Three fixes, best first:

text = "It's a fine day"        # use double quotes
text = 'It\'s a fine day'       # escape the apostrophe
text = '''It's a fine day'''    # triple quotes

The first is nearly always the right answer. Escaping works but reads badly, and once a string has several apostrophes it becomes unreadable.

Cause 4: a real newline inside a string#

message = "Dear customer,
Thank you for your order."

An ordinary string cannot span lines. Three correct versions:

# Escape sequence
message = "Dear customer,\nThank you for your order."

# Triple quotes keep the layout
message = """Dear customer,
Thank you for your order."""

# Implicit concatenation across lines
message = (
    "Dear customer, "
    "thank you for your order."
)

That last form is worth knowing: two string literals side by side are joined automatically, and the surrounding brackets let it span lines. It is the usual way to write a long message without a stray newline in it.

Cause 5: the backslash trap#

This is the one that catches people out, because the string looks perfectly closed:

path = "C:\Users\ana\"

SyntaxError: EOL while scanning string literal

The final backslash escapes the closing quote, so Python thinks the quote is part of the string and keeps looking for the real end. Any string ending in a single backslash does this.

path = "C:/Users/ana/"          # forward slashes work on Windows too
path = "C:\\Users\\ana\\"          # escaped backslashes
path = r"C:\Users\ana" + "\\"      # raw string, add the slash separately

from pathlib import Path
path = Path("C:/Users/ana")     # best - no escaping at all

Why the reported line is sometimes wrong#

Python reports where it noticed the problem, not where you made it. An unclosed quote several lines earlier can produce an error on a line that looks perfectly fine.

greeting = "Hello        # the mistake is here
name = "Ana"
print(greeting)          # but the error may point around here

When the reported line looks correct, look upwards. Syntax highlighting usually shows exactly where the string started running away.

Related errors#

An unclosed bracket produces a similar effect — Python keeps reading, and the error surfaces later than the mistake.

Avoiding it#

• Use an editor with syntax highlighting. An unclosed string is visible instantly because the colour runs on.
• Let the editor insert the closing quote. Most do this by default; type the content between them.
• Use pathlib for paths. It removes the backslash question entirely.
• Prefer double quotes. Apostrophes are far more common in English text than double quotes are.
• Use triple quotes for anything multi-line. SQL, HTML fragments, long messages.

Bonus: quotes inside f-strings#

name = "Ana"

print(f"Hello {name}")

# Before Python 3.12 you could not reuse the same quote inside the braces
data = {"name": "Ana"}
print(f"Hello {data['name']}")     # different quote inside - always works

Python 3.12 relaxed this and allows the same quote character inside the expression. Using a different one still works everywhere, so it is the safer habit if your code has to run on older versions.

Where to go next#

• Why is my Python code not working? — the other common beginner errors.
• Python string methods — what to do once the string is valid.
• Getting a file name from a path — pathlib instead of backslashes.