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

Separate traceback display from debug output level #1200

Open
bitprophet opened this Issue Sep 27, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@bitprophet
Member

bitprophet commented Sep 27, 2014

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.

@stnatic

This comment has been minimized.

stnatic commented Jan 19, 2015

Hi @bitprophet,

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 (

if fabric.state.output.debug:
) is the place where debug level is used together with printing an exception. Do you think that this is the only place (outside of tests and documentation) that needs to be adjusted?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment