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, vinay.sajip, xtreak
Date 2019-01-25.13:32:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1548423160.6.0.115582801338.issue35821@roundup.psfhosted.org>
In-reply-to
Content
That isn't quite accurate. A logger's attached handlers will always be offered a chance to handle an event if the logger's level and filters allow. However, the event is not actually passed to ancestor loggers - it is directly offered to any handlers attached to ancestor loggers, until a logger is encountered where propagate is false - and that is the last logger whose handlers are offered the event. All handlers have their own levels and filters and may or may not process an event according to those levels and filters.
History
Date User Action Args
2019-01-25 13:32:41vinay.sajipsetrecipients: + vinay.sajip, chris.jerdonek, docs@python, xtreak
2019-01-25 13:32:40vinay.sajipsetmessageid: <1548423160.6.0.115582801338.issue35821@roundup.psfhosted.org>
2019-01-25 13:32:40vinay.sajiplinkissue35821 messages
2019-01-25 13:32:40vinay.sajipcreate