[Numpy-discussion] timezones and datetime64

Daniele Nicolodi daniele@grinta....
Fri Apr 5 03:30:31 CDT 2013


On 04/04/2013 15:34, Jonathan T. Niehof wrote:
> Keeping a leap second database up to date is annoying but not as bad as 
> it could be: they're not arbitrary. Although they can occur monthly, 
> they've only ever happened at June 30 and Dec 31, announced in January 
> and July, respectively. So it would be easy to check the date of a 
> leapsecond database and warn if 1) date we're processing is after June 
> 30 of a year AND 2) LSDB older than January same year (similar checks 
> for the Dec. 31 opportunity.)

As far as I know there is no official standardization of such rules,
furthermore, how do you plan to process datetimes far in the future?

Cheers,
Daniele



More information about the NumPy-Discussion mailing list