[Python3] Fix #1445: Safe decoding of response content with try-except

[POD666]

PR checklist

• Read the contribution guidelines.
• Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
• Filed the PR against the correct branch: master, 3.4.x, 4.0.x. Default: master.
• Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

#1445

[wing328]

cc @taxpon (2017/07) @frol (2017/07) @mbohlool (2017/07) @cbornet (2017/09) @kenjones-cisco (2017/11) @tomplus (2018/10)

[tomplus]

I'm not sure if this approach is safe. Maybe we can pass binary data if we detect that raw content is returned (based on returned headers or a model).

Definitely integral tests for it are needed. We have a use case with uploading file but downloading is not tested.

[wing328]

What about using Content-Type in the HTTP response header to determine whether the data (body) is binary or not?

[POD666]

I guess a better option is to keep response data in bytes as long as possible.

[Miiike89]

Quick qusetion. Will this Fix be in the upcoming 4.0.0 Release?
In the current beta release it is not included.

[spacether]

Does this code path know anything about/use the mime type under the consumes key in the swagger spec? Those mime types can include utf-8 etc definition.

[wing328]

Updated the Python Petstore samples. Let's see if the tests pass.

[spacether]

@POD666 thank you for this PR.
I am working on cleaning up old python PRs.
Are you still interested in merging this?
Can you resolve the merge conflicts?
@wing328 why was this removed from the milestone?