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.

This issue is a reincarnation of Issue 1093 for Python 2.6, now for 3.6.

Ref: http://bugs.python.org/issue1093

What is the use case, and why is a regular for loop not enough? The bar for adding new builtin functions is high, and I don't think this meets it.

The use case is similar to the use case of sum() function, which is analogous to the sigma notation in mathematics, and is analogous to the use case of the pi notation in mathematics.

Regular loop should be equally enough to achieve the function of sum(), yet the sum() exists. Only apparent (to me) difference between the sum() and product() is that sum() is already built-in while product() is yet to be.

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.

With the existence of multiple sum() functions (and potentially multiple product() functions), would it be worth it to group these all into one module? It also doesn't help that there is an itertools.product function that has yet another purpose.

I maintain my stance that this doesn't meet the bar for entry in the builtins, but adding this to the stdlib is much more reasonable (and likely).

Actually, Guido already vetoed the idea: http://bugs.python.org/issue1093