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 skip.montanaro
Recipients ezio.melotti, r.david.murray, skip.montanaro
Date 2013-11-01.17:55:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I don't accept your conclusion. I understand that making %S consume microseconds or ".%f" be "optional" would be a load. What's the problem with forcing __str__ and isoformat to emit microseconds in all cases though? That would allow you to parse what they produce using existing code. No new constructor needed.

The issue of sometimes emitting microseconds, sometimes not, is annoying, even beyond this issue. I think for consistency's sake it makes sense for the string version of datetime and time objects to always be the same length.
Date User Action Args
2013-11-01 17:55:53skip.montanarosetrecipients: + skip.montanaro, ezio.melotti, r.david.murray
2013-11-01 17:55:53skip.montanarosetmessageid: <>
2013-11-01 17:55:53skip.montanarolinkissue19475 messages
2013-11-01 17:55:53skip.montanarocreate