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 tim.peters
Recipients mark.dickinson, rhettinger, serhiy.storchaka, skrah, steven.daprano, tim.peters
Date 2018-06-24.22:13:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Raymond, I'd say scaling is vital (to prevent spurious infinities), but complications beyond that are questionable, slowing things down for an improvement in accuracy that may be of no actual benefit.

Note that your original "simple homework problems for kids to machine learning and computer vision" doesn't include cases where good-to-the-last-bit accuracy is important, but at least in machine learning and computer vision apps primitives may be called an enormous number of times - "speed matters" to them.

Perhaps add an optional "summer" argument defaulting to __builtins__.sum?  Then the user who wants to pay more for tighter error bounds can pass in whatever they like, from a raw Kahan summer, through one of its improvements, to math.fsum.  There just isn't a "one size fits all" answer.
Date User Action Args
2018-06-24 22:13:25tim.peterssetrecipients: + tim.peters, rhettinger, mark.dickinson, steven.daprano, skrah, serhiy.storchaka
2018-06-24 22:13:25tim.peterssetmessageid: <>
2018-06-24 22:13:25tim.peterslinkissue33089 messages
2018-06-24 22:13:25tim.peterscreate