Inconsistency of BoundLogger with logging.Logger

[decaz]

There are no public attributes of logging.Logger available within BoundLogger (propagate for instance).
Also there are no attributes or methods of logging.Filterer (which is parent class of logging.Logger) available within BoundLogger.

[hynek]

That’s on purpose…what would you expect them to do?

[decaz]

@hynek I expect them to proxy to original attributes or methods.

The problem occured when I tried to replace my Flask app's default logger with BoundLogger. I use raven library and it checks propagate attribute of logger: https://github.com/getsentry/raven-python/blob/master/raven/contrib/flask.py#L297. Of course it leads to an error.

[decaz]

Another one example of logger's name attribute usage: https://github.com/aio-libs/aiohttp/blob/master/aiohttp/web.py#L394 (raises exception if BoundLogger was specified at aiohttp.web.run_app(access_log=...)).

[hynek]

I suppose the easiest way for you would be to use the dynamic default logger that will just proxy everything to the wrapped logger? I’m not sure it’s worth it to play whack-a-mole with the whole API to catch all possible usages. 🤔

[decaz]

What do you mean by "dynamic default logger" and how it can be used with the BoundLogger? Currently I just sublclassed BoundLogger and implemented methods I need to use.

[hynek]

If I’m not mistaken, it should be enough to not configure wrapper_class. Then you'll get https://www.structlog.org/en/stable/api.html#structlog.BoundLogger which will forward every unknown method call (i.e. everything except bind/unbind/new) to the wrapped logger.