We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
tl;dr users shouldn't have to deal with debug output just to see tracebacks.
Adding tracebacks to the debug level was a convenient backwards compatible way to implement tracebacks partway through the dev cycle, but it conflates two concerns which are not always tied together.
We could add this in 1.x by adding a new output level just called eg exceptions, and either way it should be kept in mind for 2.x's logging setup.
The text was updated successfully, but these errors were encountered:
I could help by adding "exceptions" log level to the 1.x (master).
I looked for output.debug in the code and there are only a few occurrences. It seems like this (
Sorry, something went wrong.
No branches or pull requests