------------------- - Ensure that `bravado` supports Windows platform - PR 415 - Ensure that responses with `application/.*` content type returns raw binary data - PR 414. Thanks Greg Ruane for your contribution!
10.3.2
------------------- - Do not warn about conflicting timeouts in requests HTTP client if only one was specified - PR 411. Thanks Pokey Rule for your contribution! - Fix bug in :class:`bravado.fido_client.FidoResponseAdapter`, it was not returning a unicode string for ``text`` - PR 412
10.3.1
------------------- - Fix :attr:`.bravado.response.BravadoResponseMetadata.is_fallback_result`, it was always ``True`` in 10.3.0 - Issue 409, PR 410 - :attr:`.bravado.response.BravadoResponseMetadata.handled_exception_info` is ``None`` again if no exception was handled - PR 410 - :mod:`bravado.testing.response_mocks` is now type-annotated - PR 410
10.3.0
------------------- - bravado is now fully type-annotated - PR 403 - Add ability to cancel a HttpFuture. Third-party HTTP clients will need to implement ``cancel`` on their :class:`.bravado.http_future.FutureAdapter` class to support this - PR 406 - The static method ``from_config_dict`` of :class:`.bravado.config.BravadoConfig` was removed due to compatibility issues with Python 3.5.0. This method was meant for internal use only; if you do happen to call it please switch to :func:`.bravado.config.bravado_config_from_config_dict` instead. - PR 407
10.2.2
------------------- - Fix issue with default (requests) HTTP client if HTTP_PROXY environment variable is set - Issue 401, PR 402. Thanks Lourens Veen for the initial report!
10.2.1
------------------- - Reraise network errors when unmarshalling - PR 397