A SyntaxError: EOL while scanning string literal means Python reached the end of a line while still inside a string literal. In other words, a string wasn’t properly closed before the line ended.
This usually happens when quotes are mismatched, or missing, or when special characters (like backslashes) confuse the parser.
In this article, we’ll cover common causes of this error and how to fix them, with code examples and explanations.
Table Of Contents 👉
Common Causes
Common reasons for this error include unclosed or mismatched quotes, unescaped special characters (especially ), and incorrect multi-line string usage. Below are the major causes and fixes:
- Unclosed or Missing Quote: Forgetting to close a string with a matching quote causes the parser to hit the end of the line inside an open string.
- Mismatched or Smart Quotes: Using the wrong kind of quote (or a copy-paste “smart” quote) can leave a string unterminated.
- Unescaped Backslash (): A trailing backslash or unescaped backslashes inside a string can escape the closing quote, leading to the string never closing.
- Multi-line String Errors: Writing a string over multiple lines without using triple quotes or proper line continuations will trigger this error.
- Raw String Limits: Using a raw string (prefix r) that ends in a backslash is not allowed and results in the same error.
- Other Cases (e.g. ast.literal_eval input): When using functions that evaluate strings, an invalid string literal inside them can cause this error.
Each of these causes is explained below with examples and fixes.
Solutions For This Error: EOL While Scanning String Literal
Solution 1: Unclosed or Missing Quote
If you start a string with a quote (” or ‘) and never close it, Python will complain at end-of-line. For example:
message = "Hello, world
# SyntaxError: EOL while scanning string literalThe string “Hello, world is never closed. Simply adding the missing quote fixes it:
message = "Hello, world"
print(message) # Outputs: Hello, worldA similar mistake is starting a string with one quote and ending with another. For example:
text = "This won't work'Here the first quote is ” but it ends with ‘, so Python never sees a matching end. Always use matching quotes.
Relevant Posts You May Like
Solution 2: Mismatched or Smart Quotes
Make sure you use straight quotes (” or ‘) and they match. Sometimes copying code from a word processor introduces “smart quotes” (like “ or ’), which Python does not recognize. For example, notice the trailing curly quote in the following (an example from a Mac):
# The last quote is a “smart quote” (`’`), not a normal single quote.
path = 'C:\some\path’
# SyntaxError: EOL while scanning string literalChanging them to normal quotes fixes the error:
path = 'C:\\some\\path' # Use normal quotes and escape backslashes.
In one case, simply replacing a smart quote with a normal double quote fixed the error.
Another issue is putting an unescaped quote inside the string. For example:
text = "He said, "Hello"."
This looks like the string ends before Hello. Instead, either use opposite quotes or escape:
text = "He said, \"Hello\"." # Use \" to include a " inside the string
# or
text = 'He said, "Hello".' # Use single quotes outside, double insideAlways ensure inner quotes are escaped or the string is enclosed in the other quote type.
Solution 3: Unescaped Backslash () Issues
Backslashes introduce escape sequences. A trailing \ at the end of a string literal will escape the closing quote, making Python think the string continues. For example:
path = "C:\Users\"
# SyntaxError: EOL while scanning string literal
The final \ escapes the closing “, so the string never ends. In a Windows path, each \ should be escaped by doubling it. For example:
path = "C:\\Users\\JohnDoe\\Documents"
Similarly, if you have any backslashes in the string, “escape” them by doubling (\). For example:
note = "Folder:\\NewFolder\\"
print(note) # Correctly escapes backslashes
Alternatively, use a raw string (prefix r) to ignore most escapes. But note: raw strings can’t end in a single backslash, because the last backslash would escape the closing quote. If you need a trailing backslash, either add another one or avoid raw string. For instance:
# Using raw string without final backslash
path = r"C:\temp\file.txt"
# If you really need a trailing backslash:
path = r"C:\temp\folder" + "\\" # add a normal backslash at endEven a simple string like “\” (backslash at end) triggers the error.
Relevant Posts You May Like
Solution 4: Multi-line String Mistakes
If you intend a string to span multiple lines, you must use triple quotes (”’ or “””) or explicit newline characters (\n). Otherwise, a newline in the middle of a quoted string causes this error. For example:
text = "This is a long string
that continues on the next line"
# SyntaxError: EOL while scanning string literal
Python sees the line break and thinks the string wasn’t closed. To fix:
- Use triple-quoted string: Triple quotes allow multi-line text natively. For example:
text = """This is a long string
that continues on the next line."""
print(text)
- Escape the newline with a backslash: You can join lines using a backslash at the end of each line:
Note the \ must be the very last character on the line.
- Use \n to insert newlines:
text = "This is a long string\nthat continues on the next line."
Another highly recommended approach is utilizing triple quotes for multi-line strings. For example:
long_string = """some
very
long
string"""
This properly encloses the text over several lines.
Conclusion
The “SyntaxError: EOL while scanning string literal” error occurs when Python reaches the end of a line before it finishes reading a string.
This is almost always due to unmatched quotes, unescaped characters (especially backslashes), or mishandled multi-line strings.
Fortunately, it’s easy to fix once you know what to look for. Double-check your quotes, escape backslashes properly, and use triple quotes for multi-line strings.
Keep an eye out for smart quotes or invisible trailing characters those are common traps too. With these tips, you’ll be able to fix this error quickly and prevent it in future projects.
Relevant Posts You May Like