Hi Vinay,
thank you for being so patient.
On 16 Jul., 01:21, Vinay Sajip [EMAIL PROTECTED] wrote:
On Jul 15, 5:17 pm, McA [EMAIL PROTECTED] wrote:
If you added the admin sink handler to the root logger, you're done.
Isn't that the first thing above? What do you mean?
I gave you a
On Jul 16, 8:55 am, McA [EMAIL PROTECTED] wrote:
Thank you for that snippet. That means, that the root-logger does
inherit
EVERY message (if it fits to the level and isn't filtered) and the
inheritage chain is build by the chosen logger names, e.g.
messages tologging.getLogger('tree.leave')
On 16 Jul., 15:38, Vinay Sajip [EMAIL PROTECTED] wrote:
On Jul 16, 8:55 am, McA [EMAIL PROTECTED] wrote:
messages tologging.getLogger('tree.leave') would also show up
inlogging.getLogger('tree') automatically?
Yes.
Ok.
Hope not to bother.
Use the propagate flag, which is mentioned
On Jul 15, 1:27 pm, McA [EMAIL PROTECTED] wrote:
Hi all,
I need a recommendation. I would to like to use theloggingmodule to
create log messages the following way:
a) Every log message does go to a admin sink.
b) Theloggingof special messages should go to the admin sink AND to
a sink
Hi Vinary,
thank you for answering. I start be proud that the author of
the logging package himself is answering. :-)
On 15 Jul., 15:51, Vinay Sajip [EMAIL PROTECTED] wrote:
On Jul 15, 1:27 pm, McA [EMAIL PROTECTED] wrote:
Add a handler to the root logger (or common_logger) to send to the
On Jul 15, 5:17 pm, McA [EMAIL PROTECTED] wrote:
If you added the admin sink handler to the root logger, you're done.
Isn't that the first thing above? What do you mean?
I gave you a choice - to add the handler to the admin_logger OR the
root logger. So I am saying here that if you added to
