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 belopolsky
Recipients belopolsky, cool-RR, facundobatista, mark.dickinson, rhettinger, vstinner
Date 2012-03-13.16:11:29
SpamBayes Score 1.8613026e-05
Marked as misclassified No
Message-id <1331655090.9.0.60760833338.issue14262@psf.upfronthosting.co.za>
In-reply-to
Content
I am -0 on the feature and -1 on the implementation.  Conversion from Decimal to float is explicit by design.  Decimal gives the user fine control over rounding issues allowing for either exact arithmetics (trapping inexact operation) or one of several rounding modes.

This said, timedelta(<decimal>) is not much worse than float(<decimal>), so I will be only -0 if the implementation is such that (1) timedelta(<decimal>) does no loose precision over the entire range of timedelta and rounding is documented; and (2) implementaton does not require an explicit import decimal inside the datetime  module.
History
Date User Action Args
2012-03-13 16:11:30belopolskysetrecipients: + belopolsky, rhettinger, facundobatista, mark.dickinson, vstinner, cool-RR
2012-03-13 16:11:30belopolskysetmessageid: <1331655090.9.0.60760833338.issue14262@psf.upfronthosting.co.za>
2012-03-13 16:11:30belopolskylinkissue14262 messages
2012-03-13 16:11:30belopolskycreate