epoch

Im working on converting epoch timestamps to dates in different timezones with pytz. What I am trying to do is create a DateTime object that accepts an Olson database timezone and an epoch time and returns a localized datetime object. Eventually I need to answer questions like "What hour was it in New York at epoch time 1350663248?" Something is not working correctly here: import datetime, pytz, time class DateTime: def __init__(self, timezone, epoch): self.timezone = timezone self.epoch = epoch timezoneobject = pytz.timezone(timezone) datetimeobject = datetime.datetime.fromtimestamp( self

How to get the current date value in epoch i.e., number of days elapsed since 1970-1-1. I need solution in unix shell script. Stephan202 Update : The answer previously posted here linked to a custom script that is no longer available, solely because the OP indicated that date +'%s' didn't work for him. Please see UberAlex' answer and cadrian's answer for proper solutions. In short: For the number of seconds since the Unix epoch use date(1) as follows: date +'%s' For the number of days since the Unix epoch divide the result by the number of seconds in a day (mind the double parentheses!): echo

I am trying to convert string in following format: 20130817T140000Z (17th Aug 2013 at 14:00) to epoch time (seconds since 1970) in an MS Excel 2013. Tried cell formatting, but it doesn't work with T and Z or the format in general. This will convert your date into somethign Excel will understand, If you have your date in Cell A1, Then convert that into Epoch Time =(DATE(LEFT(A1,4),MID(A1,5,2),MID(A1,7,2)) + TIME(MID(A1,10,2),MID(A1,12,2),MID(A1,14,2))-25569)*86400) Try this: A1=20130817T140000Z A2=DATE(LEFT(A1,4),MID(A1,5,2),MID(A1,7,2)) A3=(DATEDIF("01/01/1970 00:00:00",A2,"D")+TIME(MID(A1,10

Is the epoch start time in Python independent of the platform (i.e. always 1/1/1970)? Or is it platform dependent? I want to serialize datetimes (with second accuracy) on various machines running Python, and be able to read them back on different platforms, possibly also using different programming languages (than Python). Is serializing epoch time a good idea? The documentation says: To find out what the epoch is, look at gmtime(0) . I would interpret this to mean that no particular epoch is guaranteed. See also this Python-Dev thread . That seems to confirm the notion that, in practice, the

So I read this very interesting blog on working with datetime in Azure DocumentDb . The problem being that, right now, Azure DocumentDb does not support range search on datetime fields. The reason for that is that DocumentDb is based on json and that has no datetime type, therefore one usually puts it in a string of xml datetime format. (obviously Mongo does not have that issue, it's bson format adds the datetime type (among others)) Anyway, the article describes storing the datetime in json in an epoch (unix) time, essentially storing the datetime as an amount of seconds since 01-01-1970. One

I've been looking for a way to convert a string (in Epoch time) into a date. Basically, I need to take this: 1360440555 (in string form) and make it into this: Feb 9 12:09 2013 . I've been looking at strptime and strftime, but neither seems to be working for me. Any suggestions? Edit: Thanks, guys. I converted it to an int with atoi() , cast it as time_t , then ran ctime() on it. Worked perfectly! If only you had that value in an integer instead of a string, you could just call ctime . If only there were some way to convert a string to an integer.... time_t c; c = strtoul( "1360440555", NULL,