openstack/heat
Code Issues Proposed changes

Merge "Remove (test-)requirements-py3.txt files"

Browse Source
This commit is contained in:
Jenkins 2015-07-02 05:25:12 +00:00 committed by Gerrit Code Review
commit d53ac685d5
3 changed files with 1 additions and 68 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
requirements-py3.txt
View File

@ -1,49 +0,0 @@
# 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.
pbr<2.0,>=0.11
Babel>=1.3
dogpile.cache>=0.5.3
eventlet>=0.17.4
greenlet>=0.3.2
httplib2>=0.7.5
iso8601>=0.1.9
keystonemiddleware>=1.5.0
kombu>=3.0.7
lxml>=2.3
netaddr>=0.7.12
oslo.config>=1.11.0 # Apache-2.0
oslo.concurrency>=2.0.0 # Apache-2.0
oslo.context>=0.2.0 # Apache-2.0
oslo.db>=1.10.0 # Apache-2.0
oslo.i18n>=1.5.0 # Apache-2.0
oslo.log>=1.2.0 # Apache-2.0
oslo.messaging!=1.12.0,>=1.8.0 # Apache-2.0
oslo.middleware!=2.0.0,>=1.2.0 # Apache-2.0
oslo.serialization>=1.4.0 # Apache-2.0
oslo.service>=0.1.0 # Apache-2.0
oslo.utils>=1.6.0 # Apache-2.0
osprofiler>=0.3.0 # Apache-2.0
oslo.versionedobjects>=0.3.0
PasteDeploy>=1.5.0
posix-ipc
pycrypto>=2.6
python-ceilometerclient>=1.0.13
python-cinderclient>=1.2.2
python-glanceclient>=0.18.0
python-heatclient>=0.3.0
python-keystoneclient>=1.6.0
python-neutronclient<3,>=2.3.11
python-novaclient>=2.22.0
python-saharaclient>=0.9.0
python-swiftclient>=2.2.0
python-troveclient>=1.0.9
PyYAML>=3.1.0
requests>=2.5.2
Routes!=2.0,>=1.12.3
six>=1.9.0
SQLAlchemy<1.1.0,>=0.9.7
sqlalchemy-migrate>=0.9.6
stevedore>=1.5.0 # Apache-2.0
WebOb>=1.2.3

2
requirements.txt
View File

@ -45,7 +45,7 @@ python-swiftclient>=2.2.0
python-troveclient>=1.0.9
python-zaqarclient>=0.1.1
PyYAML>=3.1.0
qpid-python
qpid-python;python_version=='2.7'
requests>=2.5.2
Routes!=2.0,>=1.12.3
six>=1.9.0

18
test-requirements-py3.txt
View File

@ -1,18 +0,0 @@
# 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<0.11,>=0.10.0
coverage>=3.6
discover
mock>=1.0
mox>=0.5.3
oslosphinx>=2.5.0 # Apache-2.0
oslotest>=1.5.1 # Apache-2.0
paramiko>=1.13.0
psycopg2
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
testrepository>=0.0.18
testscenarios>=0.4
testtools>=1.4.0