# The order of packages is significant, because pip processes them in the order
# of appearance.
lxml!=3.7.0,>=3.4.1 # BSD
oslo.concurrency>=3.8.0 # Apache-2.0
oslo.context>=2.12.0 # Apache-2.0
oslo.i18n>=2.1.0 # Apache-2.0
oslo.log>=3.11.0 # Apache-2.0
oslo.utils>=3.20.0 # Apache-2.0
pbr>=2.0.0 # Apache-2.0
pyasn1-modules # BSD
pyasn1 # BSD
pytz>=2013.6 # MIT
requests!=2.12.2,!=2.13.0,>=2.10.0 # Apache-2.0
six>=1.9.0 # MIT
futures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD
taskflow>=2.16.0,<3.2.0 # Apache-2.0
# The order of packages is significant, because pip processes them in the order
# of appearance.
lxml!=3.7.0,>=3.4.1 # BSD
oslo.concurrency>=3.8.0 # Apache-2.0
oslo.context>=2.12.0 # Apache-2.0
oslo.i18n>=2.1.0 # Apache-2.0
oslo.log>=3.11.0 # Apache-2.0
oslo.utils>=3.20.0 # Apache-2.0
pbr>=2.0.0 # Apache-2.0
pyasn1-modules # BSD
pyasn1 # BSD
pytz>=2013.6 # MIT
requests!=2.12.2,!=2.13.0,>=2.10.0 # Apache-2.0
six>=1.9.0 # MIT
futures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD
taskflow>=2.16.0 # Apache-2.0

Remove upperbound on taskflow version
Remove upperbound on taskflow version

We added upperbound on taskflow earlier in our requirements
through change : https://morpheus.pok.stglabs.ibm.com:8443/#/c/6905/
It was done because taskflow 3.4 pulled latest networkx 2.3 which
required python 3.5.
Now in latest versions of taskflow ( from 3.6 onwards), networkx
is restricted to be < 2.3 for python 2 versions.
So, upperbound on taskflow is not required.

Change-Id: I22a5dd8e62132fdf2cad7996d7020ff5b7caa955
