Skip to content

GIT_PYTHON_TRACE to use log.debug instead of log.info #792

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.

Sign up for GitHub

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

Jump to bottom
Open
gsemet opened this issue Sep 5, 2018 · 1 comment
Open

GIT_PYTHON_TRACE to use log.debug instead of log.info #792

gsemet opened this issue Sep 5, 2018 · 1 comment
Labels
acknowledged

Comments

@gsemet
Copy link

gsemet commented Sep 5, 2018

Is it possible to change the default behavior of GIT_PYTHON_TRACE=full to use log level debug instead of INFO?

It is nice to have this trace on logging, but I would like to be able to route them to a debug.log file while keeping the stdout in INFO loglevel and higher only.

Thanks
@Byron
Copy link
Member

Byron commented Oct 14, 2018

I agree, by making it debug it probably interacts better with existing application logging, which may already use the info() channel for something less verbose than what gitpython would produce.
A patch is very welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
acknowledged
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Byron @gsemet