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 josh.r
Recipients josh.r, rhettinger, steven.daprano, tim.peters
Date 2019-02-06.02:06:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Correct me if I'm wrong, but at least initially, the first listed goal of statistics (per the PEP) was:

"Correctness over speed. It is easier to speed up a correct but slow function than to correct a fast but buggy one."

numpy already exists for people who need insane speed for these algorithms and are willing to compromise accuracy; am I wrong in my impression that statistics is more about providing correct batteries included that are fast enough for simple uses, not reimplementing numpy piece by piece for hardcore number crunching?

Even if such a function were desirable, I don't like the naming symmetry between fsum and fmean; it's kind of misleading. math.fsum is a slower, but more precise, version of the built-in sum. Having statistics.fmean be a faster, less accurate, version of statistics.mean reverses that relationship between the f-prefixed and non-f-prefixed versions of a function.
Date User Action Args
2019-02-06 02:06:08josh.rsetrecipients: + josh.r, tim.peters, rhettinger, steven.daprano
2019-02-06 02:06:06josh.rsetmessageid: <>
2019-02-06 02:06:06josh.rlinkissue35904 messages
2019-02-06 02:06:06josh.rcreate