Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=jvqn+kHXHART0Jkg7tYL+spq0AkH558NTUEVmlU/7sEu2f+SWti14X9HFotc5CJgxT2V2b6HHKS/FeQjzf1Mga/UPt15tCIkylXkfV6XFePHmkL0WdJ8C4NxzIoEjuFyIMDj68zkEf+o4IdxLQv08QBPosyJjlnQXqQ/yJkYPqY=;
References: <4F1421C3.6060806@simplistix.co.uk>
Date: Mon, 16 Jan 2012 15:08:25 +0000 (GMT)
From: Vinay Sajip <vinay_sajip@yahoo.co.uk>
Subject: Re: python loggingL filter limitation, looks intentional?
To: Chris Withers <chris@simplistix.co.uk>
In-Reply-To: <4F1421C3.6060806@simplistix.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Python List <python-list@python.org>
Precedence: list
Reply-To: Vinay Sajip <vinay_sajip@yahoo.co.uk>
Newsgroups: comp.lang.python
Message-ID: <mailman.4794.1326726512.27778.python-list@python.org>
Lines: 28
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:19040

Hi Chris,=0A=0AFiltering is intended to be for cases where integer level-ba=
sed filtering is insufficient; hence it applies to individual loggers and h=
andlers, just as the integer levels do.=A0 You are right that you would nee=
d to add a filter to all of the loggers where you want it to apply, or to a=
ll of the handlers where you want it to apply. However, if you find your us=
age pattern occurring very commonly in your applications, it's easy enough =
to create a DelegatingHandler handler class which passes its events on to a=
ny number of handlers you like. You can then apply the filter you want to a=
n instance of this handler, which you attach to your root logger.=0ARegards=
,=0A=0A=0AVinay Sajip=0A=0A=0A----- Original Message -----=0A> From: Chris =
Withers <chris@simplistix.co.uk>=0A> To: Vinay Sajip <vinay_sajip@yahoo.co.=
uk>=0A> Cc: Python List <python-list@python.org>=0A> Sent: Monday, 16 Janua=
ry 2012, 13:10=0A> Subject: python loggingL filter limitation, looks intent=
ional?=0A> =0A> Hi Vinay,=0A> =0A> It looks like this was intentional, so w=
hy was it decided that filters would =0A> only be passed messages logged to=
 the logger they're attached to rather than =0A> the all messages that end =
up getting passed to logger?=0A> =0A> For example, an app and the libraries=
 it uses log to 'some.db.driver', =0A> 'some.lib' and 'myapp'.=0A> =0A> The=
 root logger has a number of handlers attached to it.=0A> =0A> I want to wr=
ite a filter that adjusts, up or down, the level of certain messages =0A> l=
ogged based on a regex match of their message.=0A> =0A> If I understand cor=
rectly, I have to add my filter to all of the loggers above, =0A> rather th=
an just the root logger where my handlers live?=0A> =0A> Or, alternatively,=
 add the filter to all of the root handlers, thereby making =0A> the config=
uration of those handlers and/or more dependent on each other.=0A> =0A> Why=
 is that?=0A> =0A> cheers,=0A> =0A> Chris=0A> =0A> -- Simplistix - Content =
Management, Batch Processing & Python Consulting=0A> =A0 =A0 =A0 =A0 =A0 =
=A0 - http://www.simplistix.co.uk=0A>