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 Devin Jeanpierre, cvrebert, ezio.melotti, facundobatista, josh.r, mark.dickinson, rhettinger, skrah, steven.daprano, vstinner
Date 2015-01-10.02:46:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Mark Dickson wrote:
> I've talked to Mike Cowlishaw (the author of the specification)
> about this particular issue, and the spec is not likely to 
> change on this point.

I'm curious about the rationale for the decision. As I'm sure you're aware, in general 0**0 is treated as 1 by both a majority (I think) of mathematicians and programming languages. As Knuth puts it, the binomial theorem is too important to do otherwise. IEEE 754 treats it as 1, although the 2008 revision adds a second power function powr() which returns NAN if both arguments are 0. So I wonder why the decimal spec choose to do otherwise?

(Not saying they're wrong to do so.)
Date User Action Args
2015-01-10 02:46:30steven.dapranosetrecipients: + steven.daprano, rhettinger, facundobatista, mark.dickinson, vstinner, Devin Jeanpierre, ezio.melotti, cvrebert, skrah, josh.r
2015-01-10 02:46:30steven.dapranosetmessageid: <>
2015-01-10 02:46:30steven.dapranolinkissue23201 messages
2015-01-10 02:46:29steven.dapranocreate