* License : BSD-3-Clause
Programming Lang: Python 3
Description : Earth Rotation and Leap Second tables for the astropy core
package
This package provides access to the tables provided by the International
Earth Rotation and Reference Systems (IERS) service, in particular the
Earth
On Jun 22, Bruce Perens wrote
> Speaking of predictability, isn't 2000 a leap year? The rule is different
> for the turn of the century.
2000/02/29 exists. (the rule is : every for years, but not every hundred
years, but every 400 years). AFAIK.
regards, andreas
--
TO UNSUBSCRIBE FROM THIS MAIL
In <[EMAIL PROTECTED]> [EMAIL PROTECTED] (joost witteveen) writes:
>
> Now, we know the length of a year/day better, and
> only 1 in for of those turn-of-century years are leap years. Maybe that
> will change again. And about the seconds: we (currently, prossibly always)
> si
From: [EMAIL PROTECTED] (Kai Henningsen)
> Not everyone switched in 1752.
This is Pope Gregory's calendar reform, isn't it? I think it goes back a
century or more before 1752.
> Actually, it probably was a bad idea to use "leap" for both. Leap days are
> fixed by calendar design. Leap seconds a
> > Run "cal 9 1752" and tell me that.
[..]
> A more serious problem is that the current implementation doesn't allow
> for non-Christian date systems, of which there are several in active use.
> I'd expect that to be a problem for people in both parts of Jerusalem, for
> example.
>
> Does a
econd counter. If a leap second happens, you just adjust your clock (or
let xntpd do it automatically).
The difference to the other variant is that the other variant _also_ looks
at leap seconds. xntpd won't do it right, and you'll have to adjust the
rules whenever a leap second
[EMAIL PROTECTED] (Bruce Perens) wrote on 21.06.97 in <[EMAIL PROTECTED]>:
> Someone wrote:
> > This is completely unacceptable. OS time must be predictable.
>
> Run "cal 9 1752" and tell me that.
Consider it done. And now?
(Besides, isn't that a bug in cal? Not everyone switched in 1752. In fa
Someone wrote:
> This is completely unacceptable. OS time must be predictable.
Run "cal 9 1752" and tell me that.
> Can someone explain to me exactly what POSIX time is?
Posix time includes leap-year-days, but does not include the finer
resolution of leap-seconds. 21 leap-seconds (number 22 is c
On Sat, 21 Jun 1997, Mark Baker wrote:
> As it is, we use POSIX time, which means that the system time follows GMT.
> When there is a leap second the time itself is changed; the timezone
> information does not need to.
>
> > This is completely unacceptable. OS time m
il the next software upgrade.
>
> No. Using real time, the system clock increments normally, and correctly
> measures the time since the epoch. The conversion from system time to local
> time changes every time there is a leap second.
Exactly. But how does the system know about leap se
[EMAIL PROTECTED] (John Goerzen) wrote on 20.06.97 in <[EMAIL PROTECTED]>:
> What's the big deal? Why would you have to update everything? All
> you do is add an extra second to your system clock at the end of June
> and be done with it. Or you don't. Big deal.
That's when you use POSIX time
ctly
measures the time since the epoch. The conversion from system time to local
time changes every time there is a leap second.
> Then, all time stamps would suddenly change by one second (possibly
> causing FTP server remirroring and other unpleasant effects).
No, because they are based
97 in <[EMAIL PROTECTED]>:
>
> > The time is out of joint, o 'cursed spite.
> >
> > The U.S. National Institute of Standards and Technology will set it right
> > on June 30, at one second before midnight UTC, by adding a leap second.
> > Systems that ru
[EMAIL PROTECTED] (Bruce Perens) wrote on 18.06.97 in <[EMAIL PROTECTED]>:
> The time is out of joint, o 'cursed spite.
>
> The U.S. National Institute of Standards and Technology will set it right
> on June 30, at one second before midnight UTC, by adding a leap second
The time is out of joint, o 'cursed spite.
The U.S. National Institute of Standards and Technology will set it right
on June 30, at one second before midnight UTC, by adding a leap second.
Systems that run on POSIX time will ignore this. The effect is that they
will consider the diffe
15 matches
Mail list logo
