d7e70b11c6
A change to the global-requirements[1] has limited use of the monotonic library to Python versions earlier than 3.3 (later versions have built-in support for a monotonic clock), so no requirements changes can be merged until we similarly limit it in requirements.txt. [1] https://review.openstack.org/615441 Change-Id: Ib53d89ea820d21114d10280c9f4ab1b0c2c4a4bc
21 lines
841 B
Plaintext
21 lines
841 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(dhellmann): Because oslo.utils 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.utils 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
|
|
six>=1.10.0 # MIT
|
|
funcsigs>=1.0.0;python_version=='2.7' or python_version=='2.6' # Apache-2.0
|
|
iso8601>=0.1.11 # MIT
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
monotonic>=0.6;python_version<'3.3' # Apache-2.0
|
|
pytz>=2013.6 # MIT
|
|
netaddr>=0.7.18 # BSD
|
|
netifaces>=0.10.4 # MIT
|
|
debtcollector>=1.2.0 # Apache-2.0
|
|
pyparsing>=2.1.0 # MIT
|