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:00:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Personally, I don't rounding is that useful.  My working assumption is that users will select say timespec='millisecond' only when they know that their time source produces datetime instances with millisecond precision and they don't want to kill more trees by printing redundant 0's.

MAL's objection this this line of arguments was that some time sources have odd resolution (he reported MS SQL's use of 333 ms) and a user may want to have a perfect round-tripping when using a sub-usec timespec and such an odd time source or destination.
Date User Action Args
2016-03-01 22:00:35belopolskysetrecipients: + belopolsky, lemburg, gvanrossum, tim.peters, terry.reedy, vstinner, ezio.melotti, cvrebert, SilentGhost, berker.peksag, martin.panter, matrixise, jerry.elmore, acucci
2016-03-01 22:00:34belopolskysetmessageid: <>
2016-03-01 22:00:34belopolskylinkissue19475 messages
2016-03-01 22:00:34belopolskycreate