#36 [ENH] Use standard dev logging

오픈
ialbert1 주 전을 오픈 · 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
로그인하여 이 대화에 참여
레이블 없음
마일스톤 없음
No Assignees
참여자 1명
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
취소
저장
아직 콘텐츠가 없습니다.