Derived from the flake8-logging-format linter.
What it does#
Checks for redundant
exc_info keyword arguments in logging statements.
Why is this bad?#
True by default for
logging.exception calls is redundant, as is
This rule detects uses of the
logging module via a heuristic.
Specifically, it matches against:
- Uses of the
loggingmodule itself (e.g.,
import logging; logging.info(...)).
- Uses of
from flask import current_app; current_app.logger.info(...)).
- Objects whose name starts with
logor ends with
logging, when used in the same file in which they are defined (e.g.,
logger = logging.getLogger(); logger.info(...)).
- Imported objects marked as loggers via the
logger-objectssetting, which can be used to enforce these rules against shared logger objects (e.g.,
from module import logger; logger.info(...), when
logger-objectsis set to