a326ec5eea
Zoneinfo was introduced within python 3.9. The support of pytz will be removed within RHEL 10 [1]. 2023.2 (bobcat) will move our testing runtime to py3.9 and py3.10 so we want to see pytz removed within this series. tzdata is required at runtime in our gates, because, by default, zoneinfo uses the system’s time zone data if available; if no system time zone data is available, the library will fall back to using the first-party tzdata package available on PyPI. Apparently our gates have no time zone data available nor tzdata installed by default because we get the following error without tzdata installed [3]: `ModuleNotFoundError: No module named 'tzdata' So I prefer to add tzdata in our requirements to avoid runtime failure related to time zone and ensure that time zone are always available. [1] https://issues.redhat.com/browse/RHEL-219 [2] https://review.opendev.org/c/openstack/governance/+/872232 [3] https://zuul.opendev.org/t/openstack/build/0a1576775e894b09bc31269fea00ba03/log/job-output.txt#1445` Depends-on: https://review.opendev.org/c/openstack/requirements/+/875854 Change-Id: I8d87d54f6f5ded8caee6cb780bacb39afea0fea1
14 lines
619 B
Plaintext
14 lines
619 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
# NOTE(harlowja): Because oslo.serialization is used by the client libraries,
|
|
# we do not want to add a lot of dependencies to it. If you find that
|
|
# adding a new feature to oslo.serialization means adding a new dependency,
|
|
# that is a likely indicator that the feature belongs somewhere else.
|
|
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
msgpack>=0.5.2 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
tzdata>=2022.4 # MIT
|