06b5ce4573
This reverts commit a47ff0dd4abbceae786d9a5a4d1ce8042a9eb4f7. Since this merged, a global-requirements pin to keep networkx <2.0 has also merged. The plan is: 1. revert our 2.0 support and 1a. take the <2.0 pin from global requirements 2. figure out how to use constraints properly in our testing 3. restore this, with a depends-on for a 2.0 bump in requirements (which will self-test, see 3.) 4. when other projects are ready for a global 2.0 bump, merge in a controlled fashion This reverts the 2.0 support, and adds the pin for networkx <2.0 Change-Id: I18f6a1115da779581245e3dd423fd90516974a33
11 lines
389 B
Plaintext
11 lines
389 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.
|
|
Babel!=2.4.0,>=2.3.4 # BSD
|
|
networkx<2.0,>=1.10 # BSD
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
PyYAML>=3.10 # MIT
|
|
flake8<2.6.0,>=2.5.4 # MIT
|
|
six>=1.9.0 # MIT
|
|
stevedore>=1.20.0 # Apache-2.0
|