Skip to content
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

root logger's level is always set to NOTSET #3146

Closed
joelkim opened this issue Feb 27, 2018 · 1 comment · Fixed by #3960
Closed

root logger's level is always set to NOTSET #3146

joelkim opened this issue Feb 27, 2018 · 1 comment · Fixed by #3960
Labels

Comments

@joelkim
Copy link

@joelkim joelkim commented Feb 27, 2018

Currently, the log level of a root logger is always automatically re-set to NOTSET level in install_scrapy_root_handler function call if I add handlers to root logger:

logging.root.setLevel(logging.NOTSET)

Can anybody explain why this level reset is required?
This issue is relevant to issue #2352, #2149, I think.

@thernstig
Copy link
Contributor

@thernstig thernstig commented Mar 10, 2018

@joelkim please see my answer in #2149. I believe this issue can be closed as a clone of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants