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 cool-RR
Recipients belopolsky, cool-RR, facundobatista, mark.dickinson, rhettinger, skrah, vstinner
Date 2012-03-20.10:18:01
SpamBayes Score 2.5048614e-05
Marked as misclassified No
Message-id <1332238682.82.0.805468416283.issue14262@psf.upfronthosting.co.za>
In-reply-to
Content
"I'm not completly conviced by the need of supporting Decimal in timedelta constructor. Why do you use Decimal if the result should be a timedelta? Why not using timedelta directly?"

What do you mean, "Why not using timedelta directly?" How could I use timedelta directly in the timedelta constructor? I'm creating a timedelta, I don't have one ready.

I'm getting an `n_hours` variable for some component of my system. And this value happens to come as a `Decimal`. I want to create a `timedelta` out of it. So I'd want to be able to do `timedelta(hours=n_hours)` rather than `timedelta(hours=float(n_hours))`.
History
Date User Action Args
2012-03-20 10:18:03cool-RRsetrecipients: + cool-RR, rhettinger, facundobatista, mark.dickinson, belopolsky, vstinner, skrah
2012-03-20 10:18:02cool-RRsetmessageid: <1332238682.82.0.805468416283.issue14262@psf.upfronthosting.co.za>
2012-03-20 10:18:02cool-RRlinkissue14262 messages
2012-03-20 10:18:01cool-RRcreate