summaryrefslogtreecommitdiff
path: root/keystoneclient/shell.py
diff options
context:
space:
mode:
authorJamie Lennox <jamielennox@redhat.com>2013-12-17 15:30:51 +1000
committerJamie Lennox <jamielennox@redhat.com>2013-12-20 13:48:06 +1000
commita8adb476f76688106b2ac30ad5eca55e8a5efd3c (patch)
tree2ca62f2580343dfadf8216c2a642cbf8ca1c54ba /keystoneclient/shell.py
parent6ad5f2f4cc99b4d76cf0839cad09f9f8912d0542 (diff)
downloadpython-keystoneclient-a8adb476f76688106b2ac30ad5eca55e8a5efd3c.tar.gz
Remove debug specific handling
I think debug handling was initially done this way for CLI handling where we wanted to make sure only the correct information was printed to the console. However as logging.basicConfig sets up a stream handler on the root logging object I can't see any purpose to the debug handling in the actual HTTPClient. Further than this it is completely wrong that a client library is messing with it's logging level, this should be handled by an application. The debug flag is maintained and deprecated in HTTPClient and removed from the session object. There has been no release since the addition of session so there is no problem with compatibility. Change-Id: Ib00f3d93d099ed1a9dd25f17121610a7289f0061
Diffstat (limited to 'keystoneclient/shell.py')
-rw-r--r--keystoneclient/shell.py1
1 files changed, 0 insertions, 1 deletions
diff --git a/keystoneclient/shell.py b/keystoneclient/shell.py
index 62b7c68..4892248 100644
--- a/keystoneclient/shell.py
+++ b/keystoneclient/shell.py
@@ -395,7 +395,6 @@ class OpenStackIdentityShell(object):
key=args.os_key,
cert=args.os_cert,
insecure=args.insecure,
- debug=args.debug,
timeout=args.timeout)
else:
self.auth_check(args)