-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Better Logging #1691
Comments
I don't know who is gonna take on this issue but I agree. It'd be nice to have logging scope. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You might also look our discussion channels. |
Something to suppress all std out would be nice |
Any updates on this issue? |
I've started work on this and will add it to my fork eventually, but it's not a main priority at the moment. |
Thanks, let me know if i can help! |
You can redirect the output using this pattern:
|
@tadeodonegana (and others interested in this), feel free to test/review this PR: idiap#3 |
In our fork we've now switched uses of |
Problem
As of right now, all logging is done through
print
statements. When using the TTS library in different projects it spams the console on every call.Solution
Instead of print statements, a logging library should be used. Loguru or pythons standard logging library are viable options.
This would allow for better filtering using logging levels, custom handlers to allow writing log files without rerouting stdout, turn all logging off, highlight errors more clearly, etc.
The text was updated successfully, but these errors were encountered: