Repository navigation
Support programatic leap seconds #5783
Description
Currently, there's no way for astropy to programmatically change what the leap-seconds are, because the leap seconds are accessed through ERFA. This is problematic because it means when there's a new leap second we have to do a bugfix release.
The fix in Astropy itself would be pretty easy, as it can be extracted from the IERS files that we already are using for DUT1 and such. But the non-trivial part is updating ERFA to have an interface for setting the leap second - see liberfa/erfa#43 for discussion on that.
cc @mhvk
Activity
eteq commentedon Dec 3, 2018
At the astropy coordination meeting 2018, @adrn, @timj, @stargaser, et al. decided this is a good thing to prioritize for 3.2 (which means working on the
liberfafix asap). Hence the milestoning above.bsipocz commentedon Apr 17, 2019
ping @eteq - would you say at this point it's realistic to remilestone for 4.0?
mhvk commentedon Oct 4, 2019
After discussion with @eteq: The plan now is to add the ability @jwoillez created to load custom leap seconds into erfa's
dat.cinto astropy's version, so that we can experiment with it - in particular update it as needed based on the IERS tables (fromIERS_Autoby default). Then, with the interface worked out, we can push it back up toliberfaso that it is more generic and can be used elsewhere.bsipocz commentedon Oct 5, 2019
Is this now fixed with the ERFA update?
mhvk commentedon Oct 5, 2019
@bsipocz - no, not yet, we now have in principle the ability to update the leap second table, but we still need to put in place the machinery to get that updated table.
astrofrog commentedon Oct 30, 2019
Was this done in #9365?
mhvk commentedon Oct 30, 2019
Yes, fixed!