PQM outputs 'No handlers could be found for logger "bzr"'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PQM |
Confirmed
|
Medium
|
Unassigned |
Bug Description
On PQM runs at the moment, you get the following output:
No handlers could be found for logger "bzr"
This appears to be related to not setting up a default logger, as this sample python session shows:
$ python
Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import logging
>>> logger = logging
>>> l = logging.
>>> l.warning('foobar')
No handlers could be found for logger "foobar"
>>>
$ python
Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import logging
>>> logger = logging.
>>> l = logging.
>>> l.warning('foobar')
WARNING:
Attached is a diff that should address this.
Changed in pqm: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
On Tue, 2008-02-12 at 23:11 +0000, Tom Haddon wrote:
> Public bug reported:
>
> On PQM runs at the moment, you get the following output:
>
> No handlers could be found for logger "bzr"
>
> This appears to be related to not setting up a default logger, as this
> sample python session shows:
We don't want a default logger; we want a specific logger such as pqm
already sets up for itself, but in the right namespace for whatever is
logging something with no logging handlers.
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://