Message201926
| 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 |
<1383329257.92.0.868931845742.issue19475@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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" |
|