Samuele Maci

@TristanWYL I'm unsure about the error as it is the first time I see something similar. I've tried to reproduce your script on my laptop (MacOS) and I failed :(...

Reading the specs I haven't found any constraint about the presence of the `tag` and `operationId` into the operation object. I have checked the [minimal specs](http://editor.swagger.io/spec-files/minimal.yaml) and there is no...

@the-destro: I'm usually doing something similar to the following snippet to read yaml specs from file. ```python import yaml from bravado_core.spec import Spec with open(...) as f: spec_dict = yaml.load(f)...

@frankandrobot thanks for the report This seems related to https://github.com/Yelp/bravado-core/issues/281

@bobh66 could you give more context around the error that you're reporting and fixing? And potentially ways of reproducing it? ``marshal_param`` performs an initial marshaling of the value (in your...

@bobh66 now I understand your issue. The JSON serialization problem is caused by ``marshal_schema_object`` not converting the ``datetime`` object to ``str``. This happens because your specs do not specify any...

What you're describing is a problem with the specs and not an issue with the library. If the specs doesn't specify the format of a field is fair to assume...

bravado converted the string representation of a datetime (ISO8001) to a datetime because that was made explicit from specs > it was reasonable to expect bravado to accept the datetime...

@shawnsarwar bravado depends on PyYAML but it does not have requirement for a certain version of the library. Would be acceptable to add in your dependencies a min requirement for...

We need to convert headers to string because ``check_header_validity`` will raise an exception on invalid non-string headers. To make more general and avoid un-needed conversion that could lead to cases...