# 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.

# We need to pin the ansible version directly here; per the
# deprecation policy it should trail the version used by Zuul by 4
# weeks to give people time to update before these roles start
# depending on new features.  Also note we can't just include zuul
# here to pull in ansible anyway; pip doesn't actually have a
# dependency solver and the uncapped ansible requirement from
# ansible-lint pull in the latest version.
ansible>=2.7,<2.8 # https://review.opendev.org/#/c/727157/
stestr>=1.0.0,<3.0.0;python_version<'3.5' # Apache-2.0
stestr>=1.0.0;python_version>='3.5' # Apache-2.0

# For upload-logs-swift:
# TODO: openstacksdk 0.48.0 dropped python 3.5 support. Remove this constraint
# when we dropped 3.5 in zuul-jobs as well.
openstacksdk>=0.17.1,<0.48.0;python_version<'3.6' and python_version>='3'
# TODO: openstacksdk 0.46.0 dropped python 2.7 support. Remove this constraint
# when we dropped 2.7 in zuul-jobs as well.
openstacksdk>=0.17.1,<0.46.0;python_version<'3'
openstacksdk>=0.17.1;python_version>='3.6'
# TODO: keystoneauth1 4.1.0 dropped python 2.7 and 3.5 support. Remove this
# constraint when we drop them in zuul-jobs as well.
keystoneauth1>=3.18.0,<4.1.0;python_version<'3.6'

# TODO: cachetools 4.0.0 dropped python 2.7 support. Remove this constraint
# when we drop it in zuul-jobs as well.
cachetools>=2.0.0,<4.0;python_version<'3.5'
requests
requestsexceptions
bs4
# For upload-logs-google
google-cloud-storage

# For upload-logs-s3
boto3

# For upload-logs-azure
azure-storage-blob

# unittest.mock compatibility package for Python < 3.3
mock;python_version<'3.3'