Issue 12371: datetime.now() bug - Python tracker (original) (raw)

Issue12371

Created on 2011-06-20 07:41 by olrait, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
unnamed olrait,2011-06-20 07:41
Messages (2)
msg138689 - (view) Author: olrait (olrait) Date: 2011-06-20 07:41
Hello Everybody. I write you because I found a bug in datetime.now(). (tested in Python 2.6.6 -r266:84297, Aug 24 2010, 18:46:32-win32) This bug is that sometime doesn´t return milliseconds. The code to reproduce the bug is: you have to wait a lot of time (from 20 minutes to 2 hours) from datetime import datetime while True: a=str(datetime.now()) try: b=a.split(".")[1] print b except: print "exception a=%s (if you see in this case there are not the milliseconds) " % (str(a)) break I new in this . Programing and python specially. Best Regards Martin Maqueira
msg138697 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2011-06-20 10:44
str(datetime object) doesn't contain a dot if obj.microsecond equals zero. You can use obj=obj.replace(microsecond=0) to create a new datetime object using microsecond=0. Or just test that str(obj) contains a dot or not. It is not a bug in Python.
History
Date User Action Args
2022-04-11 14:57:18 admin set github: 56580
2011-06-20 10:44:20 vstinner set status: open -> closednosy: + vstinnermessages: + resolution: not a bug
2011-06-20 07:41:57 olrait create