I intended to shield the user from having to know or care about any exceptions that Requests could raise. Of course, this code doesn't do that. If you force a connection error, for example, using the NMA client, it simply causes another exception when trying to parse the result:
I think the requests module has a very clear exception hierarchy. There are few exceptions, each one with a clear scope and they all have a common father. So not sure if there is any benefit isolating the user from them.
The AttributeError exception is very misleading; getting a ConnectionError when there is a connection error is so much better! I have been using pushnotify with my small change in one of my projects for a few weeks without any issues.