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 vstinner
Recipients BreamoreBoy, aconrad, belopolsky, larry, mark.dickinson, python-dev, r.david.murray, tbarbugli, tim.peters, trcarden, vivanov, vstinner
Date 2015-09-05.20:49:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZ4ZudpE1rRtu7wYeHQJNwOdYELEcsdFEHy+kU4Fsmhkw@mail.gmail.com>
In-reply-to <1441471597.97.0.241641168782.issue23517@psf.upfronthosting.co.za>
Content
> Alex & I do agree nearest/even must be used.

Ok, so Python 3.6 should be updated to use ROUND_HALF_EVEN, and then
updated patches should be backported to Python 3.4 and 3.5. Right?

Right now, Python 3.6 uses ROUND_HALF_UP.
History
Date User Action Args
2015-09-05 20:49:31vstinnersetrecipients: + vstinner, tim.peters, mark.dickinson, belopolsky, larry, r.david.murray, aconrad, BreamoreBoy, vivanov, python-dev, tbarbugli, trcarden
2015-09-05 20:49:31vstinnerlinkissue23517 messages
2015-09-05 20:49:31vstinnercreate