RunTimeIndex

AttributeError: 'NoneType' object has no attribute … — the fix

Code called a method or read an attribute (like result.group, user.name, page.find) on a value that is None. None has no attributes at all, so the message tells you the variable’s value is wrong — the interesting question is which line made it None.

The fix, in order

1. Identify the None variable from the traceback line, then print it just above: print(repr(result)). Confirm it’s None before theorising.
2. Check the usual None-producers: re.search() / re.match() return None when there’s no match — guard with if m: before using m.group(). BeautifulSoup’s .find() returns None when the element isn’t on the page.
3. Check methods that modify in place: list.sort(), .append(), and many others return None. items = items.sort() replaces your list with None — call it on its own line.
4. Check your own functions’ return paths. A function that returns a value on the happy path but falls off the end on an error path hands the caller None. Add the missing return, or raise a clear exception instead.
5. Check lookups that quietly miss: dict.get(key) and os.environ.get(...) return None by design when the key or variable is absent — the bug is upstream, in whatever should have set it.

If it still happens

The discipline that kills this whole error family: validate values where they enter — after a search, a lookup, a parse, an API call — while you still know what “missing” means there. A clear check at the source beats a cryptic crash ten lines downstream.

Common questions

Related errors