Commit graph

13 commits

Author SHA1 Message Date
ca6a076137 Improve coverage & create InvalidContentError 2024-07-18 07:43:21 -05:00
2bd84cc2d4 fix coverage & test 2024-07-17 21:40:42 -05:00
b567f4df28 Enable more ruff checks & fix them 2024-07-07 14:57:16 -05:00
e28f83b676 Enable more ruff "DTZ" & fix them 2024-07-07 14:45:39 -05:00
54bd71ba9c Avoid boolean traps in public APIs
This is an incompatible API change, checked by ruff's "boolean trap"
family of diagnostics.
2024-07-07 14:42:37 -05:00
7957a6d5a8 Enable ruff E, F, and D tests
.. with some D tests ignored, especially conflicting ones
2024-07-07 09:44:52 -05:00
24d1b5dfaa Add a useful commandline program 2024-07-06 11:35:41 -05:00
aa0974fa79 update pre-commit 2024-05-19 18:25:52 -04:00
def8d7dc41
modernize the pre-commit 2022-10-09 12:24:57 -05:00
059e715a71
must now ensure fold=True for leap seconds 2022-10-09 12:24:50 -05:00
dd958418e4
Convert to package and add py.typed 2022-03-23 11:10:36 -05:00
96bf05b0de 3.7ism 2021-10-20 15:00:26 -05:00
8007b02dcc Add more TAI-wrangling
* leapseconddata.tai is a timezone object.  BEWARE, because of reasons,
   it compares equal to datetime.datetime.utc!

 * tai_offset can take either kind of timestamp

 * to_tai, tai_to_utc: convert to/from the TAI timescale.

 * is_leap_second: return True if the given second is a leap second.
   In the UTC timescale, the ":59" second returns True even though
   "only" the second repetition of :59 is a leap second
2021-10-20 14:44:34 -05:00
Renamed from leapseconddata_test.py (Browse further)