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 chris.jerdonek, docs@python, python-dev, vinay.sajip
Date 2013-01-21.19:53:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358798015.06.0.25326115035.issue17007@psf.upfronthosting.co.za>
In-reply-to
Content
Your suggestions are good, and I implemented them more or less as you suggested. Additional comments:

> it never makes sense to add more than one filter

Except for readability. Although in theory one filter could do the work of several, it may be that different filters are added independently from configurations based on particular requirements.

> Clarify that a handler can log the same record multiple times

I've mentioned this as *emit* the same record multiple times.

> Incidentally, is there any case where you would want the same handler to process the same record more than once?

I can't think why you'd ever want this - it would just duplicate information in the log output.

> Clarify in the LogRecord section that the "name" attribute refers to the name of the logger used in the end-user's code

I think that part is clear enough by saying that it's the name of the logger used to log the event, but I've added a rider that this is so even when the event is emitted by a handler attached to an ancestor logger.

> Clarify the last part of this sentence: "Note that filters attached to handlers are consulted ..."

Done, this should now be clearer.
History
Date User Action Args
2013-01-21 19:53:35vinay.sajipsetrecipients: + vinay.sajip, chris.jerdonek, docs@python, python-dev
2013-01-21 19:53:35vinay.sajipsetmessageid: <1358798015.06.0.25326115035.issue17007@psf.upfronthosting.co.za>
2013-01-21 19:53:35vinay.sajiplinkissue17007 messages
2013-01-21 19:53:34vinay.sajipcreate