AttributeError: 'NoneType' object has no attribute (tested)

AttributeError: 'NoneType' object has no attribute 'X' means a variable you expected to hold a real object is actually None, and you then called .X on it. Python never guesses what you meant; it fails exactly where the bad call happens, which is usually a line or two after where the value became None. We reproduced the six most common causes on a real interpreter and captured each exact traceback.

1. The error, piece by piece

'NoneType' object has no attribute 'append' tells you two things: the object on the left of the dot is None (its type is NoneType), and you tried to use .append on it, which only lists have. The fix is never to patch the attribute call — it is to find why the variable is None in the first place.

2. Six reproduced causes

All six share one root cause: a value that the code assumed was a string, list, or match object turned out to be None.

3. Cause 1: in-place list/dict methods return None

list.append(), list.sort(), dict.update(), and set.add() all mutate the object and return None — on purpose, as a signal they are in-place operations. Assigning their result is the bug:

>>> x = [1, 2, 3]
>>> y = x.append(4)   # y is None, x is now [1, 2, 3, 4]
>>> y.append(5)
AttributeError: 'NoneType' object has no attribute 'append'

Fix: don't assign the result. Use x.append(4) on its own line, then use x.

4. Cause 2: dict.get() with a missing key

dict.get(key) returns None (not an exception) when the key is absent — that is its whole point versus d[key], which raises KeyError instead. Calling a string method on the result assumes the key always exists:

>>> d = {"a": 1}
>>> v = d.get("b")
>>> v.lower()
AttributeError: 'NoneType' object has no attribute 'lower'

Fix: give .get() a default, or check first: d.get("b", "").lower() or if v is not None: v.lower().

5. Cause 3: re.match / re.search with no match

Both return None when the pattern doesn't match — they never raise. Calling .group() straight away is the most common regex bug in Python:

>>> import re
>>> m = re.match(r"\d+", "abc")
>>> m.group()
AttributeError: 'NoneType' object has no attribute 'group'

Fix: if m: m.group(), or use the walrus operator: if (m := re.match(r"\d+", s)): m.group().

6. Cause 4: a function with a missing or conditional return

A Python function with no return statement, or one that only returns inside an if, implicitly returns None on the paths that fall through. The traceback points at the call site, not the function definition, which is what makes this cause confusing to spot:

>>> def helper():
...     pass   # no return -> None
>>> r = helper()
>>> r.split(",")
AttributeError: 'NoneType' object has no attribute 'split'

>>> def maybe(s):
...     if s.startswith("x"):
...         return s
...     # falls through to None if condition is False
>>> r = maybe("abc")
>>> r.replace("a", "b")
AttributeError: 'NoneType' object has no attribute 'replace'

Fix: add an explicit return (or return None plus a caller check) on every code path, especially the "else" case you didn't think you needed.

7. Cause 5: chaining calls on a one-liner

Chaining hides the intermediate None so there is no line to put a breakpoint on:

>>> d = {}
>>> d.get("name").strip()
AttributeError: 'NoneType' object has no attribute 'strip'

Fix: split the chain into two lines while debugging (name = d.get("name"); name.strip()) so the traceback's line number tells you exactly which call returned None.

8. General fix checklist

• Read the line number in the traceback, then look at the line above it for where the value was assigned — that's almost always where the real bug is.
• Know which stdlib calls can return None on purpose: dict.get, re.match/re.search/re.fullmatch, list.append/sort/extend, dict.update, os.environ.get, and any function you wrote without a return on every path.
• Add a check before the attribute access: if value is not None:, an assert value is not None, "why", or a default value.
• In library code dealing with web pages or APIs (BeautifulSoup's .find(), requests JSON fields, database row lookups), a missing element is the single most common source of this exact error — those calls return None for "not found" instead of raising.

The JavaScript equivalent of this mistake is Cannot read properties of undefined — same root cause (reading a property off a missing value), different language's spelling of it. For the "wrong type entirely" sibling error, see ModuleNotFoundError vs ImportError.

Written with AI assistance. Measured on 2026-10-03 with Python 3.13.5 on Linux using plain python3 one-liners and small scripts under /tmp. Every traceback below is copy-pasted output, not paraphrased. PlainHeaders is our extension; Python is free.