openstack/shade
Code Issues Proposed changes

Move futures to requirements

Browse Source 
Wow. We had futures in our test-requirements so we never noticed it
wasn't in our regular requirements.

Change-Id: I6ae3434effc778524908d009627e9c0da6258f7c
This commit is contained in:
Monty Taylor 2017-03-28 07:48:17 -05:00
parent 55dd62f51f
commit 8aa8688ba8
No known key found for this signature in database
GPG Key ID: 7BAE94BC7141A594
3 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
releasenotes/notes/fix-missing-futures-a0617a1c1ce6e659.yaml Normal file
View File

@ -0,0 +1,5 @@
---
fixes:
- Added missing dependency on futures library for python 2.
The depend was missed in testing due to it having been listed
in test-requirements already.

1
requirements.txt
View File

@ -8,6 +8,7 @@ ipaddress
os-client-config>=1.25.0 os-client-config>=1.25.0
requestsexceptions>=1.1.1 requestsexceptions>=1.1.1
six six
futures;python_version<'3.2'
keystoneauth1>=2.11.0 keystoneauth1>=2.11.0
netifaces>=0.10.4 netifaces>=0.10.4

1
test-requirements.txt
View File

@ -11,4 +11,3 @@ testrepository>=0.0.17
testscenarios>=0.4,<0.5 testscenarios>=0.4,<0.5
testtools>=0.9.32 testtools>=0.9.32
reno reno
futures;python_version<'3.2'