[issue8327] unintuitive behaviour of logging message propagation

Pascal Chambon added the comment: Thanks for the doc patch, if you don't mind I'd just add the paragraph below too, to clarify the fact that logger levels are only "entry points" levels, ignored he rest of the time. There might be slight redundancies with the rest of the (long) documentation,

[issue8327] unintuitive behaviour of logging message propagation

Vinay Sajip added the comment: Documentation updated (r79876). -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue8327] unintuitive behaviour of logging message propagation

Vinay Sajip added the comment: Please see the following link for a rationale of the logging package's design: http://plumberjack.blogspot.com/2009/09/python-logging-101.html No patch to the logging system's code is planned, as it is working according to its design. The documentation will be g

[issue8327] unintuitive behaviour of logging message propagation

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8327] unintuitive behaviour of logging message propagation

New submission from Pascal Chambon : Hello Crawling into the logging module, I've just discovered its behaviour was actually far from the one I expected, in a consequent gap that the documentation had left. I thought that depending on the "propagate" parameter of each logger, a message would