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 belopolsky, elixir, ezio.melotti, gvanrossum, lemburg, r.david.murray, skip.montanaro, terry.reedy, tim.peters, vstinner
Date 2013-11-06.15:51:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
MAL: Have you thought about the rounding/truncation issues
associated with not showing microseconds ?

I believe it has to be the truncation.  Rounding is better left to the user code where it can be done either using timedelta arithmetics or at the time source.  I would expect that in the majority of cases where lower resolution printing is desired the times will be already at lower resolution at the source.
Date User Action Args
2013-11-06 15:51:03belopolskysetrecipients: + belopolsky, lemburg, gvanrossum, tim.peters, skip.montanaro, terry.reedy, vstinner, ezio.melotti, r.david.murray, elixir
2013-11-06 15:51:03belopolskysetmessageid: <>
2013-11-06 15:51:03belopolskylinkissue19475 messages
2013-11-06 15:51:02belopolskycreate