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 steven.daprano
Recipients Utkan Gezer, abarry, steven.daprano
Date 2016-07-02.12:26:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20160702122556.GO27919@ando.pearwood.info>
In-reply-to <1467459648.57.0.0102935074886.issue27439@psf.upfronthosting.co.za>
Content
On Sat, Jul 02, 2016 at 11:40:48AM +0000, Utkan Gezer wrote:
> 
> New submission from Utkan Gezer:
> 
> An issue of enhancement by the introduction of a built-in product() 
> function for the multiplication operation, functions similar to how 
> sum does for the addition operation.

I will likely be introducing an internal product() to the statistics 
module, for use in calculating the geometric mean. 

The problem with product() is similar to the problem with sum(). There 
are three different implementations of sum in the std lib: a general 
purpose one optimised for speed as the builtin, one optimized for 
floating point accuracy in the math module, and an internal-only private 
one optimized for exactness in the statistics module. I expect that 
product() will have the same tradeoffs, only even more so since it will 
overflow much more easily than sum() will.
History
Date User Action Args
2016-07-02 12:26:03steven.dapranosetrecipients: + steven.daprano, abarry, Utkan Gezer
2016-07-02 12:26:03steven.dapranolinkissue27439 messages
2016-07-02 12:26:02steven.dapranocreate