[AstroPy] Determining DST in Python?
Wayne Watson
sierra_mtnview at sbcglobal.net
Tue Dec 29 19:22:47 EST 2009
Yes, I've begun to prowl around in that murky library. It has just a
bit too much to 'easily' digest at the moment. I have used several of
the functions. I would think that someone has faced this issue
before. For the moment, the best I can think of is hard coding
dates-times for my time zone in each of the last 3 years. I think there
really only four, 2 for the past year, and 2 for prior years. I really
only need to worry about my particularly time zone, Calif.
Anne Archibald wrote:
> 2009/12/29 Wayne Watson <sierra_mtnview at sbcglobal.net>:
>
>> I'm trying to adjust a years worth of date-time stamps to UTC, and would
>> like to determine where DST starts and finishes in years from about 2006
>> to 2009. Is there an "easy" way to do this?
>>
>
> You can almost certainly do this with the standard library's datetime module:
> http://docs.python.org/library/datetime.html
>
> Anne
>
>
>> --
>> Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
>>
>> (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
>> Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
>>
>> "We're leaving you with a world that runs like
>> clockwork. And the clock it runs like is a cuckoo
>> clock." -- Frank Oppenheimer, physicist
>>
>> Web Page: <www.speckledwithstars.net/>
>>
>> _______________________________________________
>> AstroPy mailing list
>> AstroPy at scipy.org
>> http://mail.scipy.org/mailman/listinfo/astropy
>>
>>
>
>
--
Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
"We're leaving you with a world that runs like
clockwork. And the clock it runs like is a cuckoo
clock." -- Frank Oppenheimer, physicist
Web Page: <www.speckledwithstars.net/>
More information about the AstroPy
mailing list