-
-
Notifications
You must be signed in to change notification settings - Fork 16.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable logger propagation by default #1993
Conversation
I feel like a single logging handler should be used at the root. |
@untitaker you mean remove our own default handler entirely? Generelly I would like to merge this for next release. It tremendously improves what happens if you configure sentry/raven/bugsnag etc. |
Yeah exactly that. What does sentry do wrt logging? |
@untitaker sentry is not that important. Anything that configures the logging system will break currently. You can just issue |
I feel like you haven't really said what you think of this, or why it is not an alternative:
|
@untitaker as i said I'm not sure what you mean by that. Do you mean we should not configure our own log handler? Because we can't change what |
I replied with "yeah exactly that" |
Also note that I don't have any opinion on that topic, this is just for On Sun, Sep 11, 2016 at 01:24:54AM -0700, Armin Ronacher wrote:
|
I will merge this. |
I would still like to hear some sort of rationale, longer or shorter. Not because I want to educate myself at the expense of your time, but because I think it will serve as a useful reference when later this behavior will possibly be changed again. |
Main motivation for this is that
logging.basicConfig()
otherwise logsall things twice by default since the logger propagates upwards to the
default handler.
This change is