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 r.david.murray
Recipients Dave, mark.dickinson, r.david.murray, vstinner
Date 2013-02-05.23:12:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1360105921.8.0.510961645117.issue17139@psf.upfronthosting.co.za>
In-reply-to
Content
I think Victor meant "not" instead of "now".

It doesn't only occur when your run particular programs, it occurs whenever the microseconds are zero.  It is possible that your particular combination of programs produces a timing pattern that means you see microseconds zero more often in your tests.

Keep in mind that the str is a *convenience* representation.  As such it is *much* more convenient to not print the zero microseconds in the very common case of constructed datetimes that have zero microseconds.

If you want to strictly control the representation you want to use specific formatting, which you can do.  

Thus the rejection.
History
Date User Action Args
2013-02-05 23:12:01r.david.murraysetrecipients: + r.david.murray, mark.dickinson, vstinner, Dave
2013-02-05 23:12:01r.david.murraysetmessageid: <1360105921.8.0.510961645117.issue17139@psf.upfronthosting.co.za>
2013-02-05 23:12:01r.david.murraylinkissue17139 messages
2013-02-05 23:12:01r.david.murraycreate