Repository navigation
Description
Feature or enhancement
Right now none of our build bots test zoneinfo with tzdata pypi package installed.
Proof: https://github.com/python/cpython/pull/99602/files#diff-7908b1930bd1135d6f8077ef5ff578b02577f5f7042b54be88b9b86b6c7af45dR27-R35
Link to the package: https://pypi.org/project/tzdata/
However, it works locally:
(.venv) ~/Desktop/cpython issue-99508 ✔
» pip install tzdata
Collecting tzdata
Using cached tzdata-2022.6-py2.py3-none-any.whl (338 kB)
Installing collected packages: tzdata
Successfully installed tzdata-2022.6
(.venv) ~/Desktop/cpython issue-99508 ✔
» python
Python 3.12.0a2+ (heads/main:a3360facba, Nov 19 2022, 14:10:54) [Clang 11.0.0 (clang-1100.0.33.16)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import importlib.metadata
>>> importlib.metadata.metadata("tzdata")
<importlib.metadata._adapters.Message object at 0x107d5df50>
But, presence / absence of this 3rd party package change the behavior of zoneinfo module: both C and Python versions of it.
So, we need to be sure that tests can check all combinations.
Risks
Right now we don't have 3rd party packages installed for tests.
This might cause quite a lot of problems: where / how / when to install it.
It also can affect test / buildbot stability, because pip sometimes just fails to install some packages and you have to retry.
Pitch
I think we should test with tzdata PyPI package installed on at least one buildbot / CI job.
The question is: how can we do it without compromising the CI setup and reliability?
Previous discussion
- PEP 615: Add zoneinfo module #84683 (comment)
- gh-96463: fix
load_tzdataraisingOSError, not `ZoneInfoNotFound… #99602 - ZoneInfo object raises OSError instead of ZoneInfoNotFoundError for timezone input larger than 255 characters #96463
CC @pganssle
Metadata
Metadata
Assignees
Labels
Projects
- StatusShow more project fieldsDone
Activity
vstinner commentedon Nov 21, 2022
In general, I dislike that Python test suite depends on an external resources. It makes tests more error prone :-( Is it possible to mock the 3rd party tzdata package in tests?
sobolevn commentedon Nov 21, 2022
Yes, me too. I guess this can also set a bad precedent: other 3rd-party libs can be added after that as well.
I was thinking about something similar. Maybe storing some old version of it in
test_zoneinfo/test package and run tests twice: with and without it.No idea how hard it would be, because I've never seen what's inside
tzdatapackage 🤔vstinner commentedon Nov 21, 2022
I'm not talking about an hypothetical issue. For 3 weeks, I'm getting tons of email because some buildbots fail to download data from unicode.org, and so test_unicodedata fails randomly. I qualify these issues as "network issue". It happens a lot.
Browse https://mail.python.org/archives/list/buildbot-status@python.org/ and search for "test_unicodedata".
Example: https://buildbot.python.org/all/#/builders/662/builds/960
FFY00 commentedon Dec 15, 2022
As per my reply in #99602 (comment), we don't need the
tzdatapackage. It exists as a way to support data lookup when system provided tzdata is not available. We don't actually need it to test the code that loads the tzdata that way, it can be mocked. The only reason to add it would be for an integration test, which I am under the impression it's not that common here, and I don't think it's really needed, especially considering thetzdataPyPI package just repackages the tzdata from IANA, the upstream, (https://github.com/python/tzdata/blob/master/update.py) and we already test with the system provided tzdata.hugovk commentedon Jun 23, 2023
PR #19909 added
Misc/requirements-test.txtand installed it as part of.github/workflows/coverage.ymland.travis.yml.However, PRs #25679 and #30257 removed those CI files, so
Misc/requirements-test.txtis unused.Should we install it as part of another GitHub Actions workflow? (Replies on this issue suggest not.) Should we remove it?
hugovk commentedon Oct 2, 2023
Yes, let's remove
Misc/requirements-test.txt. Please see PR #110240.FFY00 commentedon Oct 13, 2023
@sobolevn do you think adding a test for
zonoinfo._common.load_tzdatausing mocks would be enough?I think we should add a test for
zonoinfo._common.load_tzdatawith mocks regardless, so that it can still be tested when thetzdatapackage is missing. We can then also add a test using thetzdatapackage, if anyone thinks it is necessary — for me, it'd be a nice to have, but probably not worth the effort on the CI maintenance.StanFromIreland commentedon Oct 2, 2025
Note that this would require installing
tzdata2020a (or 2020b, the tests still pass, 2021a introduces six failures), since that is what our extract was compiled with:cpython/Lib/test/test_zoneinfo/data/zoneinfo_data.json
Line 188 in 8797e1a
originaonxi commentedon Feb 4, 2026
StanFromIreland commentedon Feb 4, 2026
StanFromIreland commentedon Feb 21, 2026
I set up my buildbot to cover this (and all other tests that require the
'tzdata'resource).