R. David Murray added the comment: 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. ---------- nosy: +r.david.murray _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17139> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
