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-03-01.21:48:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Except for the case where you're closer than half a usec from the next value, IMO rounding makes no sense when suppressing digits. I most definitely would never want 9:59:59 to be rounded to 10:00 when suppressing seconds. If you really think there are use cases for that you could add a 'round=True' flag (as long as it defaults to False). That seems better than supporting rounding on datetime objects themselves. But I think you're just speculating.
Date User Action Args
2016-03-01 21:48:07gvanrossumsetrecipients: + gvanrossum, lemburg, tim.peters, terry.reedy, belopolsky, vstinner, ezio.melotti, cvrebert, SilentGhost, berker.peksag, martin.panter, matrixise, jerry.elmore, acucci
2016-03-01 21:48:07gvanrossumsetmessageid: <>
2016-03-01 21:48:07gvanrossumlinkissue19475 messages
2016-03-01 21:48:07gvanrossumcreate