Bringing the errors section up-to-date.

jkeyes · jkeyes · commit 885614288b49 · 2015-03-27T12:04:58.000Z
diff --git a/README.md b/README.md
@@ -393,16 +393,19 @@ Note that models generated from webhook notifications might differ slightly from
 ### Errors
 You do not need to deal with the HTTP response from an API call directly. If there is an unsuccessful response then an error that is a subclass of `intercom.Error` will be raised. If desired, you can get at the http_code of an `Error` via it's `http_code` method.
 
-The list of different error subclasses are listed below. As they all inherit off `Error` you can choose to except `Error` or the more specific error subclass:
+The list of different error subclasses are listed below. As they all inherit off `IntercomError` you can choose to except `IntercomError` or the more specific error subclass:
 
 ```python
 AuthenticationError
 ServerError
 ServiceUnavailableError
 ResourceNotFound
+BadGatewayError
 BadRequestError
 RateLimitExceeded
-AttributeNotSetError # Raised when you try to call a getter that does not exist on an object
+MultipleMatchingUsersError
+HttpError
+UnexpectedError
 ```
 
 
diff --git a/intercom/errors.py b/intercom/errors.py
@@ -1,14 +1,6 @@
 # -*- coding: utf-8 -*-
 
 
-class ArgumentError(ValueError):
-    pass
-
-
-class HttpError(Exception):
-    pass
-
-
 class IntercomError(Exception):
 
     def __init__(self, message=None, context=None):
@@ -17,6 +9,14 @@ def __init__(self, message=None, context=None):
         self.context = context
 
 
+class ArgumentError(ValueError, IntercomError):
+    pass
+
+
+class HttpError(IntercomError):
+    pass
+
+
 class ResourceNotFound(IntercomError):
     pass
 
