[issue9576] logging.addLevelName in file-based configurations

Vinay Sajip report at bugs.python.org
Fri Sep 3 12:10:07 CEST 2010


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

I set to "pending" and "wontfix" to indicate what my proposed resolution was, and to await feedback - sorry for the misunderstanding.

The custom levels feature is not intended to be used casually (as it will cause unpredictable behaviour when used differently in different third-party libraries), but there are less common application-level scenarios (where logging interoperability is less of an issue) where custom levels might be needed - which is why they are provided.

It seems acceptable to me to have different conventions for third-party code and application code. For example, NullHandler is recommended for use with third-party libraries but is not especially useful for applications.

Configuration is not intended to *completely* cover the programmatic API - just to make it easier to do the most commonly-required things.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9576>
_______________________________________


More information about the Python-bugs-list mailing list