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.

classification
Title: datetime.now() bug
Type: Stage:
Components: Versions:
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: olrait, vstinner
Priority: normal Keywords:

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:18adminsetgithub: 56580
2011-06-20 10:44:20vstinnersetstatus: open -> closed

nosy: + vstinner
messages: + msg138697

resolution: not a bug
2011-06-20 07:41:57olraitcreate