Open nelz9999 opened 6 years ago
There's a bug filed in the six
repo about this:
https://github.com/benjaminp/six/issues/45
In this report, they explicitly state
[six.u] should only be used for string literals. It's not a make-unicode-out-of-anything magic function.
Documentation on six says the same thing.
Text should always be a normal string literal.
Description
When using the python client generated by the 2.3.0 branch, in Python2, it mishandles proper JSON unicode encodings. (I believe this is probably a corner case related to @kenjones-cisco's work on #6881.)
It doesn't blow up similarly when running the client under Python3.
Swagger-codegen version
swagger-codegen-cli-2.3.0-20171204.142945-311.jar
Swagger declaration file content or url
Command line used for generation
Use the following config to build, saved as
config.json
:Then, install the client via
pip
.Steps to reproduce
Create the following file as
ex1.json
:Serve that file by running this in the same directory: