Author ned.deily
Recipients Han Shaowen, ned.deily
Date 2018-04-17.20:50:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523998245.56.0.682650639539.issue33293@psf.upfronthosting.co.za>
In-reply-to
Content
I am not sure I understand what behavior you are expecting.  But datetime.now() is documented as returning "the current local date and time" (assuming no tx= argument is provided) while datetime.utcnow() returns "the current UTC date and time".  So I would expect the two to provide a similar value only if your system/process local time zone is set to UTC.  I'm guessing the time zone in effect when your examples were run was 8 hours ahead of UTC:

>>> (1523942165.202865 - 1523913372.362377) / (60*60)
7.998011246654722

https://docs.python.org/3/library/datetime.html
History
Date User Action Args
2018-04-17 20:50:45ned.deilysetrecipients: + ned.deily, Han Shaowen
2018-04-17 20:50:45ned.deilysetmessageid: <1523998245.56.0.682650639539.issue33293@psf.upfronthosting.co.za>
2018-04-17 20:50:45ned.deilylinkissue33293 messages
2018-04-17 20:50:45ned.deilycreate