Stephan Jaensch

Isn't that just a heavier version (involving regexes) for what we're currently doing? Plus it will still cause us to call `str()` on a bytestring header value if that value...

Yeah makes sense!

@advance512 if you load a spec from a file, this will do the trick (this is how we do it internally): ````python from bravado.client import SwaggerClient from bravado.swagger_model import load_file...

@advance512 your issue is similar but different from the one the original poster discussed. You can just remove the `host` entry from your swagger spec file, bravado should use the...

@laucia: Yelp/bravado-core#97 is about fixing JSONDecodeErrors when reading JSON data submitted by the client. This is about trying to fetch swagger specs, the server returning a 500 (with a HTML...

@jakedt thanks for your contribution! Would you be able to add a few tests that verify the new behavior? Ignore the py26 test failure for now, I think we'll remove...

There are no plans currently to work on supporting version 3. That said, if you're interested please go ahead and create a pull request!

@HWiese1980 the fact that there is an OpenAPI 3.0 spec doesn't make this project deprecated. It just means you'll have to use something else to interact with OpenAPI 3 specs.

@HWiese1980 the code that does it - feel free to open a pull request! 😄

@advance512 We have support for allOf, just not in response objects. While this is regrettable it should not be too hard to implement, given that we have schema support for...