Fixes #42. Add 'raise_with' option

[prat0318]

No description provided.

[dnephin]

This seems unrelated to issue #42.

What was the reason to add this? I'm doing some refactoring of SwaggerClient, and it seems like this functionality is unnecessary. If a consumer of swagger-py wants to customize the exception, they can always try/catch in their code.

I can't find any benefit to handling this code in swagger-py itself.

[prat0318]

Yeah, it seems unrelated to #42. The only issue with client side try/catch is that all the request calls from a single client would have to be wrapped up separately each time. Adding it during client generation makes it one place declaration and less client code.

[prat0318]

It actually fixes #44.

[dnephin]

You can still do this without having to add code to swagger-py. A class decorator can wrap the entire client and handle these errors without any more code.

class ErrorHandler(object):

    def __init__(self, client, handler):
        self.client = client
        self.handler = handler

    def __getattr__(self, name):
        def operation(*args, **kwargs):
            try:
                return getattr(self.swagger_client, name)(*args, **kwargs)
            exception Exception as e:
                self.handler(name, e)

client = ErrorHandler(SwaggerClient(...), my_error_handler)

I would like to remove support for raise_with.

We could instead provide a factory to build a decorator like this from a callable

[dnephin]

I'll create a new issue