Message249849
| Author |
belopolsky |
| Recipients |
BreamoreBoy, aconrad, belopolsky, larry, mark.dickinson, python-dev, r.david.murray, tbarbugli, tim.peters, trcarden, vivanov, vstinner |
| Date |
2015年09月04日.22:43:50 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1441406630.48.0.363736737577.issue23517@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> By the way, why does Python use ROUND_HALF_EVEN for round()?
ROUND_HALF_EVEN does not introduce statistical bias in your floating point data. With this choice a randomly chosen decimal has an equal chance of being rounded up or down. I think one can prove the same for a binary float being converted to a decimal with a fixed number of places after dot. The builtin round() is a unique beast and I would have to ask Mark to know what its statistical properties are, but in general round-half-to-even is justified by the desire of not introducing a statistical bias and I don't think the natural asymmetry of the time line matters in this argument. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年09月04日 22:43:50 | belopolsky | set | recipients:
+ belopolsky, tim.peters, mark.dickinson, vstinner, larry, r.david.murray, aconrad, BreamoreBoy, vivanov, python-dev, tbarbugli, trcarden |
| 2015年09月04日 22:43:50 | belopolsky | set | messageid: <1441406630.48.0.363736737577.issue23517@psf.upfronthosting.co.za> |
| 2015年09月04日 22:43:50 | belopolsky | link | issue23517 messages |
| 2015年09月04日 22:43:50 | belopolsky | create |
|