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 Han Shaowen
Recipients Han Shaowen
Date 2018-04-17.05:20:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523942437.5.0.682650639539.issue33293@psf.upfronthosting.co.za>
In-reply-to
Content
What I am talking is like:

Python 3.6.0 (default, Feb 28 2018, 15:41:04)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import time
>>> from datetime import datetime
>>> time.time()
1523942154.3787892
>>> datetime.now().timestamp()
1523942165.202865
>>> datetime.utcnow().timestamp()
1523913372.362377

Apparently, datetime.now().timestamp() give me right unix timestamp while utcnow().timestamp() doesn't.

Fellas what do you think about this?
History
Date User Action Args
2018-04-17 05:20:37Han Shaowensetrecipients: + Han Shaowen
2018-04-17 05:20:37Han Shaowensetmessageid: <1523942437.5.0.682650639539.issue33293@psf.upfronthosting.co.za>
2018-04-17 05:20:37Han Shaowenlinkissue33293 messages
2018-04-17 05:20:37Han Shaowencreate