libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-765) Root level python logger is being set to DEBUG and console
Date Fri, 06 Nov 2015 17:57:11 GMT

    [ https://issues.apache.org/jira/browse/LIBCLOUD-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994078#comment-14994078
] 

Tomaz Muraus commented on LIBCLOUD-765:
---------------------------------------

Good catch - it looks like it's a bug which was introduced recently.

The following two lines:

{code}
if have_paramiko:
        paramiko.common.logging.basicConfig(level=paramiko.common.DEBUG)
{code}

Should be indented / nested one level deeper under the if block above. I will push a fix.

> Root level python logger is being set to DEBUG and console
> ----------------------------------------------------------
>
>                 Key: LIBCLOUD-765
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-765
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: John Bresnahan
>
> When usuing libcloud the following lines appear to set the root level python logger to
the console and to DEBUG:
> https://github.com/apache/libcloud/blob/trunk/libcloud/__init__.py#L74-L75



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message