Enhancement 1792: Use float64 as the result type for all division operations in the processing pipeline #1794
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.
Reference Issues/PRs
Closes #1792
Fixes #1791
What does this implement or fix?
Previously, dividing integers by integers in the processing pipeline (e.g. with
apply
) would perform integer division. This is true for all ofcolumn/column
,column/value
, andvalue/column
.This is not the same as the behaviour of Pandas or Polars. Worse, if the denominator was zero, this would cause a floating point exception on linux, and an integer overflow exception (#1791) on Windows.
This change makes the result a
float64
in all cases. If we want the previous behaviour to be accessible again, we should implement the integer division operator//
in Python.