Revert "client.logger.warning wrongly used in migrations"

This is a partial revert of the previous patch. The inline setup of
the logger ends up causing issues when this is consumed by other
libraries that want control over the logger.

Closes-Bug: #1697452

This reverts commit 9a272014167390217351dd5a60f50f518f4ae600.

Change-Id: I1d61d4952aef1039e72a2aac629cb13a6a15d7b2
This commit is contained in:
Sean Dague 2017-06-15 10:26:41 -04:00
parent 4bdc6003db
commit ddb386b2df

View File

@ -183,11 +183,7 @@ class Client(object):
self.server_external_events = \ self.server_external_events = \
server_external_events.ServerExternalEventManager(self) server_external_events.ServerExternalEventManager(self)
if not logger: self.logger = logger or logging.getLogger(__name__)
logger = logging.getLogger(__name__)
if not logger.handlers:
logger.addHandler(logging.StreamHandler())
self.logger = logger
# Add in any extensions... # Add in any extensions...
if extensions: if extensions: