datetime.timestamp() loses an time (an hour)

user_8881748 0
Viewed 2055

I encountered this issue but found the solution after a bit of research. I have posted my answer below to show my findings. If anyone has alternative suggestions please post them.

I needed to convert a datetime.datime object to a Unix timestamp. I tried using the datetime.timestamp. I found the result was 1 hour behind what I expected. I was able to replicate this issue with the following.

from datetime import datetime, timestamp
dt = datetime.utcfromtimestamp(1438956602.0)

dt now equals datetime.datetime(2015, 8, 7, 14, 10, 2)

Then:

dt_stamp = datetime.timestamp(dt)

Which gives dt_stamp = 1438953002.0 (which is different from our original timestamp). If we convert it back to datetime

datetime.utcfromtimestamp(dt_stamp)

We get:

datetime.datetime(2015, 8, 7, 13, 10, 2)

Which is an hour earlier than our original time.

For context I am using Python 3 and based in Britain where we're currently using British summer time (1 hour ahead of UTC).

My solution can be found below. If you think I have missed anything from my explanation or there's a better solution, please post your own answer.

python-datetime python-3.x timestamp datetime python
3 Answers

I met the same problem recently, my case is that part EDF recording from one hostipal in UK have one hour bias, which is considered due to British summer time.
Following is the solution to my case.

from datetime import datetime as dt

Please use

dt = dt.utcfromtimestamp(#YOUR_TIME_STAMP)

INSTEAD of

dt = dt.fromtimestamp(#YOUR_TIME_STAMP)
user_145638570

The cause for this difference is actually shown in the datetime.timestamp documentation.

Naive datetime instances are assumed to represent local time and this method relies on the platform C mktime() function to perform the conversion. Since datetime supports wider range of values than mktime() on many platforms, this method may raise OverflowError for times far in the past or far in the future.

Because I am in UTC+1 (during British summer time) this is the timezone datetime.timestamp uses to calculate the timestamp. This is where the mistake comes in. The documentation recommends a few ways to deal with this. I went with the following.

from datetime import datetime, timestamp
dt = datetime.utcfromtimestamp(1438956602.0)
dt_stamp = datetime.timestamp(dt.replace(tzinfo=timezone.utc))

By adding .replace(tzinfo=timezone.utc) to the end of dt it specifies that this is done in the UTC timezone. datetime.timestamp then knows to use the UTC time rather than whatever timezone my machine is running.

People in America or other parts of the world will encounter this issue if not using the UTC timezone. If this is the case you can set tzinfo to whatever your timezone is. Also note that datetime.utcfromtimestamp is also clearly designed for people using the UTC timezone.

user_88817480

I think you need a so called aware datetime object. Aware means it nows the time difference you have:

datetime.fromtimestamp(timestamp, timezone(timedelta(hours=1)))

Try it with that line of code, where timestamp is your Unix timestamp.

user_86394440
Related