[
https://issues.apache.org/jira/browse/LIBCLOUD-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994104#comment-14994104
]
ASF subversion and git services commented on LIBCLOUD-765:
----------------------------------------------------------
Commit a64678aa875d0d1966ce7b0748782eb2d34b4f7c in libcloud's branch
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=a64678a ]
Fix a bug / regression with Libcloud accidentaly setting paramiko root logger
level to DEBUG (this should only happen if LIBCLOUD_DEBUG environment variable)
is provided.
Part of LIBCLOUD-765, reported by John Bresnahan.
> 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)
