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 ezio.melotti
Recipients doerwalter, ezio.melotti, georg.brandl, pitrou, r.david.murray, tim.peters
Date 2009-11-20.07:08:50
SpamBayes Score 3.1398392e-07
Marked as misclassified No
Message-id <>
If __str__ is supposed to produce "nice" output, the microsecond shouldn't 
be visible at all imho (special cases are not special enough to break the 
If the date/time object is read by a human he probably doesn't care of 
the microseconds anyway, if it's parsed by a machine the '0 microseconds' 
situation must be special-cased to avoid failures like the one mentioned in 
the first message.
The fact that the documentation of datetime.isotime() mentions it is not 
enough if the user doesn't know that it's used by str(), so a note should be 
added to the doc.
I don't know if/how the situation can be fixed though.
Date User Action Args
2009-11-20 07:08:53ezio.melottisetrecipients: + ezio.melotti, tim.peters, doerwalter, georg.brandl, pitrou, r.david.murray
2009-11-20 07:08:52ezio.melottisetmessageid: <>
2009-11-20 07:08:51ezio.melottilinkissue7342 messages
2009-11-20 07:08:50ezio.melotticreate