#36 [ENH] Use standard dev logging

Открыто
открыта 1 неделю назад ialbert · комментариев: 0
ialbert прокомментировал 1 неделю назад

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
Войдите, чтобы присоединиться к обсуждению.
Нет меток
Нет этапа
Нет назначенных лиц
1 участников
Срок выполнения

Срок выполнения не установлен.

Зависимости

В настоящее время эта задача не имеет зависимостей.

Загрузка…
Отмена
Сохранить
Пока нет содержимого.