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 gvanrossum
Recipients SilentGhost, acucci, belopolsky, berker.peksag, cvrebert, ezio.melotti, gvanrossum, jerry.elmore, lemburg, martin.panter, matrixise, terry.reedy, tim.peters, vstinner
Date 2016-02-25.18:29:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJKMCZ+=cM42MGjPBJ04zevqaM_JWDryD4uQkBMT86cTRA@mail.gmail.com>
In-reply-to <1456424149.8.0.313863125597.issue19475@psf.upfronthosting.co.za>
Content
Out of context here, but regarding round vs. truncate, IIUC for time
truncating down is the norm. My digital clock shows "12:00" for the
duration of the minute starting at noon. People look for clocks to
flip to know when it is exactly a given time (if the clock is accurate
enough).
History
Date User Action Args
2016-02-25 18:29:22gvanrossumsetrecipients: + gvanrossum, lemburg, tim.peters, terry.reedy, belopolsky, vstinner, ezio.melotti, cvrebert, SilentGhost, berker.peksag, martin.panter, matrixise, jerry.elmore, acucci
2016-02-25 18:29:22gvanrossumlinkissue19475 messages
2016-02-25 18:29:22gvanrossumcreate