Improve logging in Python client

[wing328]

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.1.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

For #236

cc @taxpon @frol @mbohlool @cbornet @kenjones-cisco

[asqui]

Your changes to resources/python/configuration.mustache look good to me but not sure why there are 64 other files changed in the same commit.

Looks like that might be the result of re-generating the petstore sample, in which case it might be better to commit the results of that separately?

[wing328]

@asqui the updated Petstore samples need to be included in this PR so that the CI can test the changes in the Python petstore clients.

[kenjones-cisco]

LGTM! Thanks @wing328

[asqui]

@wing328 I understand that, but what I don't understand is how all those petstore example changes are at all related to your code change.

[wing328]

@asqui good question. The Python samples may not be up-to-date due to new test cases added to the test spec.

[grokify]

@asqui Would having 2 commits in this PR satisfy your concern in the future? For example, one commit could be the client code changes and another commit could be the updated samples. This way the two commits could be viewed separately while also including the updated samples for testing.

[wing328]

The CircleCI error is not related.