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 SilentGhost, acucci, belopolsky, berker.peksag, cvrebert, ezio.melotti, gvanrossum, jerry.elmore, lemburg, martin.panter, matrixise, terry.reedy, tim.peters, vstinner
Date 2016-03-01.22:09:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I feel odd trying to advocate a POV that I disagree with, so let me just quote MAL:

In practice you often don't know the resolution of
the timing source. Nowadays, the reverse of what you said
is usually true: the source resolution is higher than the
precision you use to print it.

For full seconds, truncation will add an error of +/- 1 second,
whereas rounding only adds +/- 0.5 seconds. This is what convinced
me to use rounding instead of truncation.

I somehow missed this argument when Marc-Andre made it, so I want to make sure that it is properly considered before we finalize this issue.
Date User Action Args
2016-03-01 22:09:32belopolskysetrecipients: + belopolsky, lemburg, gvanrossum, tim.peters, terry.reedy, vstinner, ezio.melotti, cvrebert, SilentGhost, berker.peksag, martin.panter, matrixise, jerry.elmore, acucci
2016-03-01 22:09:32belopolskysetmessageid: <>
2016-03-01 22:09:32belopolskylinkissue19475 messages
2016-03-01 22:09:32belopolskycreate