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 tim.peters
Recipients ezio.melotti, r.david.murray, skip.montanaro, tim.peters
Date 2013-11-01.18:07:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The decision to omit microseconds when 0 was a Guido pronouncement, back when datetime was first written.  The idea is that str() is supposed to be friendly, and for the vast number of applications that don't use microseconds at all, it's unfriendly to shove ".000000" in their face all the time.  Much the same reason is behind why, e.g., str(2.0) doesn't produce "2.0000000000000000".

I doubt this will change.  If you want to use a single format, you could massage the data first, like

if '.' not in dt:
    dt += ".000000"
Date User Action Args
2013-11-01 18:07:37tim.peterssetrecipients: + tim.peters, skip.montanaro, ezio.melotti, r.david.murray
2013-11-01 18:07:37tim.peterssetmessageid: <>
2013-11-01 18:07:37tim.peterslinkissue19475 messages
2013-11-01 18:07:37tim.peterscreate