Hacker News new | past | comments | ask | show | jobs | submit login

That doesn't change the situation of past leap seconds in any way, those still need to be accounted for.



The nice thing is that you would have a static table of leap seconds, and would not need to poll a URL to check for new leap second data (as Astropy does, for example, on import!).


Do you also need to account for rubber seconds in the pre-1972 version of UTC?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: