change hacking requirements and fix hacking problems

Change-Id: I3dcdc9630a60b6ef550530cc729f846605a1ec44

openstack/image/v2/image.py

@@ -40,4 +40,4 @@ class Image(resource.Resource):
     tags = resource.prop('tags')
     updated_at = resource.prop('updated_at')
     virtual_size = resource.prop('virtual_size')
-    visibility = resource.prop('visibility')
+    visibility = resource.prop('visibility')

openstack/tests/unit/database/v1/test_user.py

@@ -66,4 +66,4 @@ class TestUser(testtools.TestCase):
 
         user.User.create_by_id(sess, CREATING, path_args=path_args)
         sess.post.assert_called_with(url, service=user.User.service,
-                                     json=payload)
+                                     json=payload)

openstack/tests/unit/image/v2/test_image.py

@@ -63,4 +63,4 @@ class TestImage(testtools.TestCase):
         self.assertEqual(EXAMPLE['tags'], sot.tags)
         self.assertEqual(EXAMPLE['updated_at'], sot.updated_at)
         self.assertEqual(EXAMPLE['virtual_size'], sot.virtual_size)
-        self.assertEqual(EXAMPLE['visibility'], sot.visibility)
+        self.assertEqual(EXAMPLE['visibility'], sot.visibility)

openstack/tests/unit/test_resource.py

@@ -1161,7 +1161,7 @@ class ResourceMapping(base.TestCase):
         self._test_resource_serialization("patch", "update_by_id")
 
 
-class FakeResponse:
+class FakeResponse(object):
     def __init__(self, response):
         self.body = response
 

test-requirements.txt

@@ -1,7 +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>=0.9.2,<0.10
+hacking>=0.10.0,<0.11
 
 coverage>=3.6
 discover