scale() "lies" about its scale factor about graphite-web HOT 4 CLOSED

another effect of this, is that for scale(...,5) the output becomes scale(...,5.0) , even though case isn't as bad, I would still argue the returned target string should display the factor how I choose to display it

from graphite-web.

This is probably just because its a float being printed to 2 decimal
places. I'll check glyph.py for the culprit.
On Nov 15, 2012 1:28 PM, "Dieter Plaetinck" [email protected]
wrote:

another effect of this, is that for scale(...,5) the output becomes
scale(...,5.0) , even though case isn't as bad, I would still argue the
returned target string should display the factor how I choose to display it

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/103#issuecomment-10421581.

from graphite-web.

Btw according to @sivy it seems like it does the same for movingAverage, but it's actually worse:
when he specifies windowSize 30, graphite claims it was '30.0' instead of '30' (i don't really understand why because the code does the code does "%d" % 30 which should really yield "30", and he's using 0.9.9)
if you actually specify 30.0 then graphite complains like so https://gist.github.com/522f5c20ea3103719207

from graphite-web.

I've switched this to %g which should do the right thing, though it'll use scientific notation after 4 decimal places. To satisfy that, i've fixed the grammar to parse scientific notation as well here: ae910ae

from graphite-web.