Message170771
| Author |
Alexander.Belopolsky |
| Recipients |
Alexander.Belopolsky, belopolsky, cool-RR, facundobatista, mark.dickinson, rhettinger, skrah, vstinner |
| Date |
2012年09月19日.20:57:19 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7h-xbGcPBe_Lmm+Q5veyAsQ0w42H9y0_U=-sa92BhT_+uc0Q@mail.gmail.com> |
| In-reply-to |
<1348086727.38.0.15645123586.issue14262@psf.upfronthosting.co.za> |
| Content |
On Wed, Sep 19, 2012 at 4:32 PM, Ram Rachum <report@bugs.python.org> wrote:
> But that number, 1.15, is stored in a Django decimal field.
My criticism was towards the idea that one may need to multiply
timedelta by a dollar amount or convert a dollar amount to a
timedelta. Storing dollar amounts is an important use case for
Decimal and there are several reasons why Decimal is a better choice
than float for this. On the other hand, I don't see why use of
Decimal would be required in your example.
Do you have any real world use cases where Decimal is clearly
preferred over float and there is a need to multiply Decimals by time
deltas? |
|