➜

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 acucci
Recipients SilentGhost, acucci, belopolsky, berker.peksag, cvrebert, ezio.melotti, gvanrossum, jerry.elmore, lemburg, martin.panter, matrixise, terry.reedy, tim.peters, vstinner
Date 2016-02-22.18:15:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456164941.94.0.409000011121.issue19475@psf.upfronthosting.co.za>
In-reply-to
Content 
New patch after @martin.panter comments on Rietveld. I left only this:

- ``'milliseconds'``: Append the hours, minutes, seconds and milliseconds.

> vadmium 2016/02/21 23:30:20
> I think this should explain that fractions are truncated to zero, never 
> rounded
> up. At least for fractions of milliseconds, although this could apply 
> to the
> other options as well.

I think is quite obvious that a datetime.now() can't be rounded to the future if microseconds are 999500.
History
Date User Action Args
2016-02-22 18:15:42acuccisetrecipients: + acucci, lemburg, gvanrossum, tim.peters, terry.reedy, belopolsky, vstinner, ezio.melotti, cvrebert, SilentGhost, berker.peksag, martin.panter, matrixise, jerry.elmore
2016-02-22 18:15:41acuccisetmessageid: <1456164941.94.0.409000011121.issue19475@psf.upfronthosting.co.za>
2016-02-22 18:15:41acuccilinkissue19475 messages
2016-02-22 18:15:41acuccicreate