taskflow/requirements.txt
Joshua Harlow d33b3165b7 Just unify having a single requirements.txt file
The difference between the py2 and py3 requirements file
is marginal and it does not harm py3 from having additional
dependencies that aren't used anyway so just have a single
requirements file.

Change-Id: I969ea61f68a2c7c2d7fb4d38e6e1d3daa59b0d40
2015-03-29 22:48:42 -07:00

37 lines
959 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.
# See: https://bugs.launchpad.net/pbr/+bug/1384919 for why this is here...
pbr>=0.6,!=0.7,<1.0
# Packages needed for using this library.
# Only needed on python 2.6
ordereddict
# Python 2->3 compatibility library.
six>=1.9.0
# Enum library made for <= python 3.3
enum34
# Very nice graph library
networkx>=1.8
# Used for backend storage engine loading.
stevedore>=1.3.0,<1.4.0 # Apache-2.0
# Backport for concurrent.futures which exists in 3.2+
futures>=2.1.6
# Used for structured input validation
jsonschema>=2.0.0,<3.0.0
# For common utilities
oslo.utils>=1.4.0,<1.5.0 # Apache-2.0
oslo.serialization>=1.4.0,<1.5.0 # Apache-2.0
# For deprecation of things
debtcollector>=0.3.0,<0.4.0 # Apache-2.0