| 2006-08-29 00:59:02 |
Etienne Goyer |
bug |
|
|
added bug |
| 2006-08-29 14:07:47 |
John A Meinel |
description |
bzr selftest give the following warning :
o handlers could be found for logger "bzr.paramiko"
Output of "bzr selftest" attached. Paramiko 1.5.2 is installed. |
bzr selftest give the following warning :
No handlers could be found for logger "bzr.paramiko"
Output of "bzr selftest" attached. Paramiko 1.5.2 is installed. |
|
| 2006-08-29 14:07:47 |
John A Meinel |
title |
Warning 'o handlers could be found for logger "bzr.paramiko"' during selftest |
Warning 'No handlers could be found for logger "bzr.paramiko"' during selftest |
|
| 2006-10-10 05:32:00 |
John A Meinel |
bzr: status |
Unconfirmed |
Fix Released |
|
| 2006-10-10 05:32:00 |
John A Meinel |
bzr: importance |
Undecided |
Low |
|
| 2006-10-10 05:32:00 |
John A Meinel |
bzr: statusexplanation |
|
The specific error is indicative of not having logging setup, and paramiko trying to log something through logging.getLogger().
With paramiko 1.6.2 (current) and bzr.dev, I was not able to reproduce this, so either we are always initializing logging, or paramiko is doing something better.
For now, I think we have fixed it. |
|
