-
Notifications
You must be signed in to change notification settings - Fork 1.1k
django-debug-toolbar should not (un)set root logger level #572
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
Labels
Comments
I don't know why it's implemented like this. See also #563. |
+1 |
blueyed
added a commit
to blueyed/django-debug-toolbar
that referenced
this issue
Jan 29, 2015
blueyed
added a commit
to blueyed/django-debug-toolbar
that referenced
this issue
Jan 29, 2015
While they are conflicting, I don't think they are two different implementations of the same thing. #563 exists to prevent memory leaks when running with |
Indeed @tim-schilling they do not solve the same issue, so they should be merged somehow. I was just pointing out it was not that simple. 😃 |
ryneeverett
pushed a commit
to ryneeverett/django-debug-toolbar
that referenced
this issue
Oct 2, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had a hard time figuring out why the root logger level (
logging.root.level
) was being reset to 0 (NOTSET).This gets done by DDT:
https://github.com/django-debug-toolbar/django-debug-toolbar/blob/master/debug_toolbar/panels/logging.py#L53
I think that DDT should not change this setting, but only add its handler.
There might be a configuration option for this, but then you could also just configure your root handler accordingly.
The text was updated successfully, but these errors were encountered: