Author underrun
Recipients underrun, vinay.sajip
Date 2013-08-12.17:16:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1376327765.17.0.481681682107.issue18689@psf.upfronthosting.co.za>
In-reply-to
Content
dictConfig and fileConfig are nice for static needs, but when I want to quickly enable a complex (but not complicated) logging flow I find it just as tedious as the current situation with the direct API.

> ... as at the very least every handler would need to be changed to accommodate the new kwarg

Adding a keyword only argument to the base handler and the other handler classes is a nearly trivial change in terms of lines and complexity of the code.

> Also, this isn't going to work for third-party handlers which are out there already, since they won't necessarily recognise a new kwarg.

I don't see that as a problem. If 3rd party handlers are intelligent then they will include **kargs in their __init__ and pass that forward to the initialization of their parent. If they haven't done so then nothing changes for them and they just support exactly the same features they supported previously.
History
Date User Action Args
2013-08-12 17:16:05underrunsetrecipients: + underrun, vinay.sajip
2013-08-12 17:16:05underrunsetmessageid: <1376327765.17.0.481681682107.issue18689@psf.upfronthosting.co.za>
2013-08-12 17:16:05underrunlinkissue18689 messages
2013-08-12 17:16:05underruncreate