This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients LwarX, josm, luke-jr, vinay.sajip
Date 2009-06-22.14:42:29
SpamBayes Score 0.00011470419
Marked as misclassified No
Message-id <1245681751.32.0.596579974203.issue1711603@psf.upfronthosting.co.za>
In-reply-to
Content
Why would you want to use a single handler instance against multiple
loggers? It's safe to do so, but you could get duplicated messages
appearing. I presume you have reviewed the documentation and are aware
that loggers are organised in a hierarchy and that in the normal case,
handlers of all parent loggers are allowed to handle events logged with
a particular logger.

What do you mean by "single stream in multiple handlers"? In general
this could result in garbled output, if you have multiple threads in
your environment.

Are these questions relevant to this SysLogHandler issue? I couldn't see
a connection with your earlier comment. If not relevant, please post
them on comp.lang.python where you will probably get more people looking
at them, so that the quality of answers is likely to be more helpful to you.
History
Date User Action Args
2009-06-22 14:42:31vinay.sajipsetrecipients: + vinay.sajip, josm, luke-jr, LwarX
2009-06-22 14:42:31vinay.sajipsetmessageid: <1245681751.32.0.596579974203.issue1711603@psf.upfronthosting.co.za>
2009-06-22 14:42:30vinay.sajiplinkissue1711603 messages
2009-06-22 14:42:29vinay.sajipcreate