Skip to content

Commit a442794

Browse files
Update tzdata to version 2026c (#145)
# Version 2026.3 Upstream version 2026c released 2026-07-08T17:23:58+00:00 ## Briefly: Alberta moved to permanent -06 on 2026-06-18. Morocco moves to permanent +00 on 2026-09-20. More integer overflow bugs have been fixed in zic. ## Changes to future timestamps Alberta’s 2026-03-08 spring forward was its last foreseeable clock change, as it moved to permanent -06 thereafter. (Thanks to Roozbeh Pournader and others.) Model this with its traditional abbreviation CST. Although the change to permanent -06 legally took place on 2026-06-18, temporarily model the change to occur on 2026-11-01 at 02:00 instead, for the same reason we introduced a similarly temporary hack for British Columbia in 2026b. Although another TZDB release will likely be needed soon because Northwest Territories will likely follow Alberta, the legal formalities have not yet taken place. Morocco plans to move back to permanent UTC, without daylight saving time transitions, on 2026-09-20 at 02:00. This also affects Western Sahara. ## Changes to commentary Northwest Territories is expected to move to permanent -06 prior to 2026-11-01 02:00, when clocks would otherwise fall back. (Thanks to Tim Parenti and James Bellaire.) Model this with its traditional abbreviation CST. Unfortunately the change is not yet official, so it is currently present only as comments that can be uncommented as needed. Co-authored-by: Stan Ulbrych <stan@python.org>
1 parent 8f35937 commit a442794

15 files changed

Lines changed: 104 additions & 142 deletions

File tree

NEWS.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,37 @@
1+
# Version 2026.3
2+
Upstream version 2026c released 2026-07-08T17:23:58+00:00
3+
4+
## Briefly:
5+
6+
Alberta moved to permanent -06 on 2026-06-18. Morocco moves to permanent +00 on
7+
2026-09-20. More integer overflow bugs have been fixed in zic.
8+
9+
## Changes to future timestamps
10+
11+
Alberta’s 2026-03-08 spring forward was its last foreseeable clock change, as it
12+
moved to permanent -06 thereafter. (Thanks to Roozbeh Pournader and others.)
13+
Model this with its traditional abbreviation CST. Although the change to
14+
permanent -06 legally took place on 2026-06-18, temporarily model the change to
15+
occur on 2026-11-01 at 02:00 instead, for the same reason we introduced a
16+
similarly temporary hack for British Columbia in 2026b.
17+
18+
Although another TZDB release will likely be needed soon because Northwest
19+
Territories will likely follow Alberta, the legal formalities have not yet taken
20+
place.
21+
22+
Morocco plans to move back to permanent UTC, without daylight saving time
23+
transitions, on 2026-09-20 at 02:00. This also affects Western Sahara.
24+
25+
## Changes to commentary
26+
27+
Northwest Territories is expected to move to permanent -06 prior to 2026-11-01
28+
02:00, when clocks would otherwise fall back. (Thanks to Tim Parenti and James
29+
Bellaire.) Model this with its traditional abbreviation CST. Unfortunately the
30+
change is not yet official, so it is currently present only as comments that can
31+
be uncommented as needed.
32+
33+
---
34+
135
# Version 2026.2
236
Upstream version 2026b released 2026-04-23T06:06:43+00:00
337

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
2026.2
1+
2026.3

news.d/2026b.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Version 2026.2
2+
Upstream version 2026b released 2026-04-23T06:06:43+00:00
3+
4+
## Briefly:
5+
6+
British Columbia moved to permanent -07 on 2026-03-09. Some more overflow bugs
7+
have been fixed in zic.
8+
9+
## Changes to future timestamps
10+
11+
British Columbia’s 2026-03-08 spring forward was its last foreseeable clock
12+
change, as it moved to permanent -07 thereafter. (Thanks to Arthur David Olson.)
13+
Although the change to permanent -07 legally took place on 2026-03-09,
14+
temporarily model the change to occur on 2026-11-01 at 02:00 instead. This
15+
works around a limitation in CLDR v48.2 (2026-03-17). This temporary hack is
16+
planned to be removed after CLDR is fixed.

news.d/2026c.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Version 2026.3
2+
Upstream version 2026c released 2026-07-08T17:23:58+00:00
3+
4+
## Briefly:
5+
6+
Alberta moved to permanent -06 on 2026-06-18. Morocco moves to permanent +00 on
7+
2026-09-20. More integer overflow bugs have been fixed in zic.
8+
9+
## Changes to future timestamps
10+
11+
Alberta’s 2026-03-08 spring forward was its last foreseeable clock change, as it
12+
moved to permanent -06 thereafter. (Thanks to Roozbeh Pournader and others.)
13+
Model this with its traditional abbreviation CST. Although the change to
14+
permanent -06 legally took place on 2026-06-18, temporarily model the change to
15+
occur on 2026-11-01 at 02:00 instead, for the same reason we introduced a
16+
similarly temporary hack for British Columbia in 2026b.
17+
18+
Although another TZDB release will likely be needed soon because Northwest
19+
Territories will likely follow Alberta, the legal formalities have not yet taken
20+
place.
21+
22+
Morocco plans to move back to permanent UTC, without daylight saving time
23+
transitions, on 2026-09-20 at 02:00. This also affects Western Sahara.
24+
25+
## Changes to commentary
26+
27+
Northwest Territories is expected to move to permanent -06 prior to 2026-11-01
28+
02:00, when clocks would otherwise fall back. (Thanks to Tim Parenti and James
29+
Bellaire.) Model this with its traditional abbreviation CST. Unfortunately the
30+
change is not yet official, so it is currently present only as comments that can
31+
be uncommented as needed.

src/tzdata/__init__.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# IANA versions like 2020a are not valid PEP 440 identifiers; the recommended
22
# way to translate the version is to use YYYY.n where `n` is a 0-based index.
3-
__version__ = "2026.2"
3+
__version__ = "2026.3"
44

55
# This exposes the original IANA version number.
6-
IANA_VERSION = "2026b"
6+
IANA_VERSION = "2026c"
-1.1 KB
Binary file not shown.
-1.1 KB
Binary file not shown.
343 Bytes
Binary file not shown.
343 Bytes
Binary file not shown.
343 Bytes
Binary file not shown.

0 commit comments

Comments
 (0)