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 njs
Recipients MJH, ezio.melotti, jab, jyasskin, mark.dickinson, njs, serhiy.storchaka, tim.peters, vstinner
Date 2018-09-27.06:15:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538028944.48.0.545547206417.issue32956@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, I hadn't noticed this change in py3, but it would never have occurred to me that it's controversial... I thought everyone who'd studied the issue agreed that round-half-to-even was the best default :-). Numpy has always done round-to-even, and it's the default rounding mode mandated by IEEE754. (This doesn't mean that they mandate that round() itself follow this rule, but the implicit rounding that all floating point operations do has to follow this rule.) See also: https://en.wikipedia.org/wiki/Rounding#Round_half_to_even
History
Date User Action Args
2018-09-27 06:15:44njssetrecipients: + njs, tim.peters, mark.dickinson, vstinner, jyasskin, ezio.melotti, jab, serhiy.storchaka, MJH
2018-09-27 06:15:44njssetmessageid: <1538028944.48.0.545547206417.issue32956@psf.upfronthosting.co.za>
2018-09-27 06:15:44njslinkissue32956 messages
2018-09-27 06:15:44njscreate