This repository has been archived by the owner on Sep 6, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running with
DEBUG=0
this isn't a problem, but withDEBUG=1
, these py-cord loggers produce a LOT of output. We're not really interested in seeing this and it mostly just clutters our actually useful internal debug logs. This therefore explicitly drops the log level on these loggers to INFO or even WARNING.Note:
Another option would be to suppress all
discord
loggers completely, at least down to INFO, rather than focusing on the very spammy ones. I'm not sure this is a good idea, since some of the logs are pretty nice to see, like thediscord.client
ones, producing a log whenever an event occurs.