This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients mark.dickinson, pablogsal, rhettinger, tim.peters, veky
Date 2020-08-03.17:27:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The existing already has a separate code path for floats.  The proposal is to add an overflow/underflow check to that existing path so that we don't get nonsense like 0.0, 1e+175, or Inf depending on the data ordering.  That doesn't warrant a separate function.

FWIW fsum() is a separate function for several reasons, none of which apply to the current proposal:  1) we didn't already have a math.sum().  2) All inputs types get converted to float.  3) Even in common cases, it is measurably slower that sum().  4) It has a different signature than sum().
Date User Action Args
2020-08-03 17:27:23rhettingersetrecipients: + rhettinger, tim.peters, mark.dickinson, veky, pablogsal
2020-08-03 17:27:23rhettingersetmessageid: <>
2020-08-03 17:27:23rhettingerlinkissue41458 messages
2020-08-03 17:27:23rhettingercreate