#36 [ENH] Use standard dev logging

Otwarty
otworzone 1 tydzień temu przez ialbert · 0 komentarzy
ialbert skomentował 1 tydzień temu

We’ve got a janky BaseCog.log method but it would be better to use a more standard logging mechanism. Python seems to have something for this natively.

Goals:

  • More granularity for debug, info, warn, error severity levels
  • Domain constraints so that log levels for different cogs or other functional areas can be adjusted for debugging
  • Log levels changeable at runtime so bot doesn’t need to be restarted or need code changes
  • Message templating so expensive string interpolation is deferred until after the log level checks have determined the message will actually be shown
We've got a janky BaseCog.log method but it would be better to use a more standard logging mechanism. Python seems to have something for this natively. Goals: - More granularity for debug, info, warn, error severity levels - Domain constraints so that log levels for different cogs or other functional areas can be adjusted for debugging - Log levels changeable at runtime so bot doesn't need to be restarted or need code changes - Message templating so expensive string interpolation is deferred until after the log level checks have determined the message will actually be shown
Zaloguj się, aby dołączyć do tej rozmowy.
Brak etykiety
Brak kamienia milowego
Brak przypisanych
1 uczestników
Due Date

No due date set.

Zależności

This issue currently doesn't have any dependencies.

Ładowanie…
Anuluj
Zapisz
Nie ma jeszcze treści.