Re: ANN: leapseconds-announced-2009
Bjorn Buckwalter wrote:
leapseconds-announced is a pragmatic, if imperfect, improvement over my past practices. It provides a LeapSecondTable with all leap seconds announced to date (hence the name). Once the IERS announces[3] another leap second the package will need an update and all code using it a recompile. While this precludes its use in long-running production applications it is eminently adequate for my one-off uses or for applications that can afford to recompile infrequently.
You should consider using the tz database, which provides a leap-seconds table in the "right/UTC" timezone (and much other useful information). -- Ashley Yakeley
On Sun, Jan 18, 2009 at 00:00, Ashley Yakeley
Bjorn Buckwalter wrote:
leapseconds-announced is a pragmatic, if imperfect, improvement over my past practices. It provides a LeapSecondTable with all leap seconds announced to date (hence the name). Once the IERS announces[3] another leap second the package will need an update and all code using it a recompile. While this precludes its use in long-running production applications it is eminently adequate for my one-off uses or for applications that can afford to recompile infrequently.
You should consider using the tz database, which provides a leap-seconds table in the "right/UTC" timezone (and much other useful information).
Thanks for the pointer. My "source" is the Earth Orientation Parameter (EOP) data at http://www.celestrak.com/SpaceData/; specifically I autogenerate the module from http://www.celestrak.com/SpaceData/eop19620101.txt. Probably looks more complicated than necessary but I'm parsing the file anyway for other purposes. -Bjorn
On Sun, 2009-01-18 at 00:34 -0500, Bjorn Buckwalter wrote:
Thanks for the pointer. My "source" is the Earth Orientation Parameter (EOP) data at http://www.celestrak.com/SpaceData/; specifically I autogenerate the module from http://www.celestrak.com/SpaceData/eop19620101.txt. Probably looks more complicated than necessary but I'm parsing the file anyway for other purposes.
With tz, though, you could discover the table at run-time and so be more likely to be up to date. -- Ashley Yakeley
On Sun, Jan 18, 2009 at 00:37, Ashley Yakeley
On Sun, 2009-01-18 at 00:34 -0500, Bjorn Buckwalter wrote:
Thanks for the pointer. My "source" is the Earth Orientation Parameter (EOP) data at http://www.celestrak.com/SpaceData/; specifically I autogenerate the module from http://www.celestrak.com/SpaceData/eop19620101.txt. Probably looks more complicated than necessary but I'm parsing the file anyway for other purposes.
With tz, though, you could discover the table at run-time and so be more likely to be up to date.
Ah yes. However, just like "time" this library does not attempt to solve that particular problem. The purpose of leapseconds-announced is to be dead easy to use (no IO and treading of the LeapSecondTable to the usage point), at the cost of longevity. Of course, as I pointed out in the announcement this trade-off isn't suitable for all applications. -Bjorn
participants (2)
-
Ashley Yakeley -
Bjorn Buckwalter