New submission from Han Shaowen <bolide2...@gmail.com>: 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? ---------- components: Extension Modules messages: 315377 nosy: Han Shaowen priority: normal severity: normal status: open title: Using datetime.datetime.utcnow().timestamp() in Python3.6.0 can't get correct UTC timestamp. type: behavior versions: Python 3.6 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33293> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com