Update tzdata to version '2026b'#135
Merged
StanFromIreland merged 2 commits intomasterfrom Apr 24, 2026
Merged
Conversation
Member
Author
|
I had to force push as my commit title said 2025... it seems everyone is making such mistakes with this release ;-) |
StanFromIreland
commented
Apr 24, 2026
Member
Author
StanFromIreland
left a comment
StanFromIreland
left a comment
There was a problem hiding this comment.
Released RC to TestPyPI, all looks good and tests pass.
Co-authored-by: Stan Ulbrych <stan@python.org>
StanFromIreland
changed the title
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.
Version 2026.2
Upstream version 2026b released 2026-04-23T06:06:43+00:00
Briefly:
British Columbia moved to permanent -07 on 2026-03-09. Some more overflow bugs
have been fixed in zic.
Changes to future timestamps
British Columbia’s 2026-03-08 spring forward was its last foreseeable clock
change, as it moved to permanent -07 thereafter. (Thanks to Arthur David Olson.)
Although the change to permanent -07 legally took place on 2026-03-09,
temporarily model the change to occur on 2026-11-01 at 02:00 instead. This
works around a limitation in CLDR v48.2 (2026-03-17). This temporary hack is
planned to be removed after CLDR is fixed.