[Proposal] Preserving the type returned by the aggregator for mean, avg, and median instead of coercing to an int. #2868
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
visidata’s current behavior for average, mean, and median is to coerce the result to a float which works fine for the builtin types but doesn’t play nice when adding custom precision preserving types, like Python’s
Fraction
, andDecimal
types.It would also be possible to replace
sum(vals) / len(val)
by Python’s nativestatistics.mean
which also preserves the int type when possible:statistics.mean([1, 2]) # 1.5 (float)
statistics.mean([1, 2, 3]) # 2 (int)
But that would mean that two golden files have to change since they would lose some
.00
.