Message 106381 - Python tracker

➜

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	stutzbach
Recipients	belopolsky, mark.dickinson, mcherm, rhettinger, stutzbach, tim.peters, vstinner
Date	2010-05-24.19:50:01
SpamBayes Score	0.0053002564
Marked as misclassified	No
Message-id	<1274730603.91.0.569804569669.issue1289118@psf.upfronthosting.co.za>
In-reply-to

Content
I don't have a strong feeling about the method of rounding. My thinking is: If my application is sensitive to how the last microsecond is rounded, then I shouldn't be using a type that only gives me 1-microsecond precision. (Likewise, if my application is sensitive to how the last binary digital of the floating point mantissa is rounded ... I'm in trouble) That said, round-to-nearest strikes me as the least-surprising approach.

I don't have a strong feeling about the method of rounding.  My thinking is: If my application is sensitive to how the last microsecond is rounded, then I shouldn't be using a type that only gives me 1-microsecond precision.

(Likewise, if my application is sensitive to how the last binary digital of the floating point mantissa is rounded ... I'm in trouble)

That said, round-to-nearest strikes me as the least-surprising approach.

History
Date	User	Action	Args
2010-05-24 19:50:04	stutzbach	set	recipients: + stutzbach, tim.peters, mcherm, rhettinger, mark.dickinson, belopolsky, vstinner
2010-05-24 19:50:03	stutzbach	set	messageid: <1274730603.91.0.569804569669.issue1289118@psf.upfronthosting.co.za>
2010-05-24 19:50:01	stutzbach	link	issue1289118 messages
2010-05-24 19:50:01	stutzbach	create