openstack/oslo.messaging
Code Issues Proposed changes

warn against sorting requirements

Browse Source 
Change-Id: I64ae9191863564e278a35d42ec9cd743a233028e
Addresses-Bug: #1365061
This commit is contained in:
Doug Hellmann 2014-09-03 14:23:10 -04:00
parent a9ec73f38d
commit b9a917c2e2
4 changed files with 16 additions and 0 deletions

4
requirements-py3.txt

@ -1,3 +1,7 @@
# 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.
oslo.config>=1.2.1 oslo.config>=1.2.1
oslo.utils>=0.2.0 oslo.utils>=0.2.0
stevedore>=0.14 stevedore>=0.14

4
requirements.txt

@ -1,3 +1,7 @@
# 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.
oslo.config>=1.4.0.0a3 oslo.config>=1.4.0.0a3
oslo.utils>=0.2.0 oslo.utils>=0.2.0
stevedore>=0.14 stevedore>=0.14

4
test-requirements-py3.txt

@ -1,3 +1,7 @@
# 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 already pins down pep8, pyflakes and flake8 # Hacking already pins down pep8, pyflakes and flake8
hacking>=0.9.1,<0.10 hacking>=0.9.1,<0.10

4
test-requirements.txt

@ -1,3 +1,7 @@
# 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 already pins down pep8, pyflakes and flake8 # Hacking already pins down pep8, pyflakes and flake8
hacking>=0.9.2,<0.10 hacking>=0.9.2,<0.10