Change approach to calculate offset_to_tz_ids#207
Open
Conversation
The previous approach relied on sampling from the current date back to a cutoff date using an arbitrary step (40 days) That meant that depending on the time of year the process run it could hit different offsets for the same timezone, leading to inconsistent results. The new approach uses pytz transition data directly which should be deterministic.
marcospri
commented
Jan 8, 2026
| ): | ||
| cutoff = datetime.datetime(self.RECENT_YEARS_START, 1, 1) | ||
|
|
||
| # Find the last transition before cutoff to get the offset active at cutoff |
Contributor
Author
There was a problem hiding this comment.
I did this after finding an issue with pacific/norfolk
marcospri
commented
Jan 8, 2026
| "Asia/Nicosia", | ||
| "Asia/Qatar", | ||
| "Asia/Riyadh", | ||
| "Asia/Tbilisi", |
Contributor
Author
There was a problem hiding this comment.
I worked out a few differences in the data and it's down to these two. I can live with that.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The previous approach relied on sampling from the current date back to a cutoff date using an arbitrary step (40 days)
That meant that depending on the time of year the process run it could hit different offsets for the same timezone, leading to inconsistent results.
The new approach uses pytz transition data directly which should be deterministic.
Found this after finding a change on the json files without any other apparent changes.
The new approach might be overkill, or at least the code is more verbose but I find "iterate over a TZ db" clearer than "step back in time 40 days at a time".
_get_latest_tz_namesalso uses the step back in time. If we merge a version of this I'll try to apply there too.