Too many decimal places in output about client_python

[beorn7]

I can't speak for the Python library, but at least the Go client library represents floats in a way that exactly the same IEEE-754 representation is created on the server side. The Go client would naturally use protobuf between machines, so one could easily thing the text format is just informational and for humans. The Python client, however, only speaks the text format, so arguably it's made for machines, too.

[bernardosulzbach]

I see. And if there are machines reading this output - I suppose there are, right? - it cannot be polished.

[brian-brazil]

The current output is a bit eager to use scientific notation, but we need as full precision as we can't predict user use cases (maybe they're measuring something in nanoseconds) and advertise 64bit float support.

Even if there were an output format intended entirely for humans, we'd still display as much precision as we could.

[bernardosulzbach]

Understood. So this is going to stay as it currently is.