[issue28443] Logger methods never use kwargs

Vinay Sajip added the comment: I'll close this - as indicated in my comment, there's no need for this enhancement, as the already available "extra" parameter performs the same function. -- resolution: -> wont fix status: open -> closed ___ Python t

[issue28443] Logger methods never use kwargs

Stéphane Wirtel added the comment: In your patch, there is an assignation to self.kwargs = kwargs but you don't use it into your code. Maybe with inheritance ? -- nosy: +matrixise ___ Python tracker _

[issue28443] Logger methods never use kwargs

Vinay Sajip added the comment: Those signatures have **kwargs for potential extension of the logging API itself (without extending the existing argument list), not for passing arguments to filters. You can already filter completely flexibly by passing additional values in the "extra" paramet

[issue28443] Logger methods never use kwargs

Changes by Jordan Brennan : -- components: +Library (Lib) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue28443] Logger methods never use kwargs

Changes by Jordan Brennan : -- components: -Argument Clinic ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue28443] Logger methods never use kwargs

Changes by R. David Murray : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue28443] Logger methods never use kwargs

New submission from Jordan Brennan: The methods on the Logger class e.g. logger.debug all accept **kwargs, these are passed to the _log method but they are never used. If _log attached them as an attribute to the LogRecord object, it would allow for creation of more powerful Filter objects to