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 tim.peters
Recipients cryvate, gabhcosta, tim.peters
Date 2021-07-17.23:41:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1626565301.23.0.809107631349.issue44663@roundup.psfhosted.org>
In-reply-to
Content
> It looks like the difference one would expect from (fast) human input)

Nope, the timestamps in the original report are about 3 hours apart (10808+ seconds).

Reports like these are often much clearer if they state the timezone of the system they're running on.

Plausible here: as the docs say, `utcnow()` returns a _naive_ datetime - no timezone info is attached.

But `.timestamp()`:

"""
Naive datetime instances are assumed to represent local time 
"""

So I _expect_ the results to differ unless the box this is running on uses UTC as its local time.

On my box, in native timezone CDT, the two ways are 5 hours apart, which is indeed CDT's offset from UTC.
History
Date User Action Args
2021-07-17 23:41:41tim.peterssetrecipients: + tim.peters, cryvate, gabhcosta
2021-07-17 23:41:41tim.peterssetmessageid: <1626565301.23.0.809107631349.issue44663@roundup.psfhosted.org>
2021-07-17 23:41:41tim.peterslinkissue44663 messages
2021-07-17 23:41:40tim.peterscreate