https://stackoverflow.com/search?q=%22NoneType+object+has+no... - ~900 cases of people spending time to upload their code to SO and waiting for answers with explanations, rather than trying to understand what the error means. (or even reading the first link that comes up in "Questions that may already have your answer")
As for copy-pasting error-messages into google, the results may not apply, in the asker's mind, to what they are doing. The results might have information which is too technical to understand. If the error comes from a turgid framework, it might very well provide no useful clue at all because its just detritus from leaky framework abstractions.
http://stackoverflow.com/questions/19671962/uncaught-error-i...
Luckily, I was met with a kind and thoughtful answer, and it turns out that I'm probably not the only one with the problem: the question has had some 42K views. But I've been coding for 20+ years, and I still screwed up my question. Yes, even on a Q&A site, folks should research before posting. But some grace to beginners who don't even know the proper etiquette would go a long ways.
Though Google does seem a little worse at programming queries now than it was circa 2009. :/
Seymour Cray once said he liked to hire inexperienced engineers, because they don't know what's supposed to be impossible.
All the basic questions have pretty much been answered quite thoroughly already. Any beginner is extremely unlikely to ask something that someone else hasn't already thought of.