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.

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

It must not always print errors #23

Closed
xcash opened this issue Jul 23, 2013 · 2 comments
Closed

It must not always print errors #23

xcash opened this issue Jul 23, 2013 · 2 comments

Comments

@xcash
Copy link
Contributor

xcash commented Jul 23, 2013

Hi there.
When the library is used in a daemon it is disruptive that it prints errors to stderr.
You can disable automatic printing of warnings but not errors.

Could you introduce an errors flag like warnings?

I can do it and make a pull request if you accept this suggestion.
@timotheus
Copy link
Owner

Makes sense to me. I'd just want it to log errors by default since many people run into configuration issues when first using the SDK. Go ahead and submit the pull request and I'll merge it in. Thanks!

@xcash
Copy link
Contributor Author

xcash commented Jul 23, 2013

Ok i'll do it with .get('errors', True) then :)

@xcash xcash closed this as completed Jul 25, 2013
timotheus pushed a commit that referenced this issue Apr 11, 2017
@xcash
added errors flag to api initialization issue #23
0c44226
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@timotheus @xcash