This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients eric.araujo, tarek, vinay.sajip
Date 2010-09-03.10:10:04
SpamBayes Score 7.27953e-08
Marked as misclassified No
Message-id <1283508607.12.0.667987504071.issue9576@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2010-09-03 10:10:07vinay.sajipsetrecipients: + vinay.sajip, tarek, eric.araujo
2010-09-03 10:10:07vinay.sajipsetmessageid: <1283508607.12.0.667987504071.issue9576@psf.upfronthosting.co.za>
2010-09-03 10:10:05vinay.sajiplinkissue9576 messages
2010-09-03 10:10:04vinay.sajipcreate