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 Devin Jeanpierre
Recipients Devin Jeanpierre, ezio.melotti, facundobatista, josh.r, mark.dickinson, rhettinger, skrah
Date 2015-01-09.03:37:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420774663.86.0.460868959368.issue23201@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, also, it is documented: https://docs.python.org/3/library/decimal.html#decimal.InvalidOperation

Still, the status quo is bad. At the very least there should be clear documentation on how Decimal differs in behavior from floats and ints. (Other than the obvious, like 1/5 taking on a different value -- although explicitly mentioning that in the list might be a good idea.)

BTW, 0**0=1 is not mathematically impure. It at one point was fairly well accepted as the right answer, since it's the one that tends to come out naturally . e.g. http://arxiv.org/abs/math/9205211 page 6 ("ripples") . This might explain why ints and floats so casually evaluate 0**0 to 1.
History
Date User Action Args
2015-01-09 03:37:43Devin Jeanpierresetrecipients: + Devin Jeanpierre, rhettinger, facundobatista, mark.dickinson, ezio.melotti, skrah, josh.r
2015-01-09 03:37:43Devin Jeanpierresetmessageid: <1420774663.86.0.460868959368.issue23201@psf.upfronthosting.co.za>
2015-01-09 03:37:43Devin Jeanpierrelinkissue23201 messages
2015-01-09 03:37:43Devin Jeanpierrecreate