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 doerwalter, ezio.melotti, georg.brandl, pitrou, r.david.murray, tim.peters
Date 2009-11-17.22:13:27
SpamBayes Score 1.9733136e-05
Marked as misclassified No
Message-id <1258496009.84.0.200285365909.issue7342@psf.upfronthosting.co.za>
In-reply-to
Content
This behavior is intentional and is documented in the
datetime.isoformat() docs:

"""
Return a string representing the date and time in ISO 8601 format,
YYYY-MM-DDTHH:MM:SS.mmmmmm or, if microsecond is 0, YYYY-MM-DDTHH:MM:SS 
...
"""

It was Guido's idea ;-)  The point is that __str__ is supposed to
produce "nice" output, and ".0000000" was thought to be more annoying
than useful, since the common case is that datetime objects don't use
microseconds.
History
Date User Action Args
2009-11-17 22:13:29tim.peterssetrecipients: + tim.peters, doerwalter, georg.brandl, pitrou, ezio.melotti, r.david.murray
2009-11-17 22:13:29tim.peterssetmessageid: <1258496009.84.0.200285365909.issue7342@psf.upfronthosting.co.za>
2009-11-17 22:13:27tim.peterslinkissue7342 messages
2009-11-17 22:13:27tim.peterscreate