Not quite sure I follow. logging doesn't have a default level. The library/module writer chooses from: DEBUG, INFO, WARNING, ERROR, CRITICAL. The module writer is not supposed to choose what gets emitted, the user of the library chooses what levels to emit.

verbose had more levels at the DEBUG and INFO levels than logging, not fewer. i.e. it had debug and debug-annoying, and helpful and silent, though I can't see the latter is ever used.

Are you concerned about module writers not knowing what level to set a message at? I guess I'd hope the review process would help police that.

As for matplotlib setting what gets emitted, I'd agree that we only do that from the command line or if the correct rcParams are set, and that we deprecate those parameters in favour of top-level users simply turning on the correct logging options in their top-level program.

Just as a taste for how I'd propose this works, consider the text.py example that started this. The "warning" would now be:

    if not np.isfinite(posx) or not np.isfinite(posy):
                log = logging.getLogger(__name__)
                log.warning("posx and posy should be finite values not rendering text")
                return

The __name__ will make this logger have the hierarchical name matplotlib.text, as would any other calls to the logger from the text module.

WARNING and above are emitted by default by logging. If the user wants to suppress warnings from matplotlib:

logger = logging.getLogger('matplotlib')
logger.setLevel(logging.ERROR)

If they just want to suppress the warning in text:

logger = logging.getLogger('matplotlib.text')
logger.setLevel(logging.ERROR)

Uh oh!

Description

Enhancement suggestion

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions