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 chris.jerdonek
Recipients chris.jerdonek, docs@python
Date 2019-01-24.20:07:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
In-reply-to
Content
Currently, the logging docs are a bit ambiguous or at least not completely clear as to when events are propagated when Logger.propagate is true. The docs currently say [1]--

"If [the `propagate`] attribute evaluates to true, events logged to this logger will be passed to the handlers of higher level (ancestor) loggers, in addition to any handlers attached to this logger."

But it's not clear if "logged to this logger" means (1) a log method like info() or error() was called on the logger, or (2) the event was passed to the logger's handlers (i.e. satisfied the logger's log level threshold and any filters).

Empirically, I found that the meaning is (2).

[1]: https://docs.python.org/3/library/logging.html#logging.Logger.propagate
History
Date User Action Args
2019-01-24 20:07:21chris.jerdoneksetrecipients: + chris.jerdonek, docs@python
2019-01-24 20:07:19chris.jerdoneksetmessageid: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
2019-01-24 20:07:19chris.jerdoneklinkissue35821 messages
2019-01-24 20:07:19chris.jerdonekcreate