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

hacking>=3.0.1,<3.1.0

alembic==1.0.1
amqp<2.7,>=2.6.0
beaker==1.10.0
cryptography>=2.7
deepdiff==3.3.0
falcon==1.4.1
jsonpath-ng==1.4.3
jsonschema==4.0.0a2
keystoneauth1>=3.18.0
keystonemiddleware==5.3.0
kombu<4.7,>=4.6.10
networkx==2.2
oslo.cache==1.38.1
oslo.concurrency==3.28.1
oslo.config==7.0.0
oslo.context>=2.21.0
oslo.messaging==9.1.1
oslo.db==4.41.1
oslo.log==3.45.2
oslo.middleware==3.36.0
oslo.policy==1.40.1
oslo.serialization==2.29.2
oslo.utils==3.42.1
pbr==5.4.5
PasteDeploy==1.5.2
Paste==3.0.1
psycopg2-binary==2.8.4
pylibyaml~=0.1
pyyaml~=5.1
python-dateutil>=2.8.1

# TODO(alanmeadows)
# this must match the container service
# likely this should be imported from a
# container sidecar long-term
python-barbicanclient==4.7.0
python-keystoneclient==3.22.0
python-memcached==1.59

Routes==2.4.1
six>=1.15.0
stevedore>=1.30.0
urllib3==1.25.9
uwsgi~=2.0.19.1
# To support profiling in non-prod
Werkzeug==0.16.1