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, ned.deily, tim.peters
Date 2018-04-18.03:01:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1524020495.39.0.682650639539.issue33293@psf.upfronthosting.co.za>
In-reply-to
Content
Guys, what I said is the doc in help(datetime.timestamp) is 'Return POSIX timestamp as float.' So I assumed it is irrelevant to time zone, considering POSIX timestamp's definition. If it is then datetime.now and datetime.utcnow should return the same timestamp. But datetime.now().timestamp return a correct timestamp which I checked in the website https://www.unixtimestamp.com/ but datetime.utcnow().timestamp did not.

:)
History
Date User Action Args
2018-04-18 03:01:35Han Shaowensetrecipients: + Han Shaowen, tim.peters, ned.deily
2018-04-18 03:01:35Han Shaowensetmessageid: <1524020495.39.0.682650639539.issue33293@psf.upfronthosting.co.za>
2018-04-18 03:01:35Han Shaowenlinkissue33293 messages
2018-04-18 03:01:34Han Shaowencreate