jepler/leapseconddata
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Make the 'is tai' check not depend on object identity

Browse source 
.. because the identity of the 'tai' object can be lost when
the multiprocessing module gets involved.
This commit is contained in:
Jeff Epler 2022-11-05 17:34:44 -05:00
parent 16198dc6b7
commit 168426a4c6
No known key found for this signature in database
GPG key ID: D5BF15AB975AB4DE
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
leapseconddata/__init__.py
View file

@ -59,6 +59,11 @@ def _from_ntp_epoch(value: int) -> datetime.datetime:
return NTP_EPOCH + datetime.timedelta(seconds=value)
def datetime_is_tai(when: datetime.datetime) -> bool:
"""Return true if the datetime is in the TAI timescale"""
return when.tzname() == "TAI"
@dataclass(frozen=True)
class LeapSecondData:
"""Represent the list of known and scheduled leapseconds
@ -113,7 +118,7 @@ class LeapSecondData:
the offset of the last list entry.
"""
is_tai = when.tzinfo is tai
is_tai = datetime_is_tai(when)
if not is_tai:
when = self._utc_datetime(when)
if check_validity:
@ -142,7 +147,7 @@ class LeapSecondData:
:param check_validity: Check whether the database is valid for the given moment
Naive timestamps are assumed to be UTC. A TAI timestamp is returned unchanged."""
if when.tzinfo is tai:
if datetime_is_tai(when):
return when
when = self._utc_datetime(when)
return (when + self.tai_offset(when, check_validity)).replace(tzinfo=tai)