[melbourne-pug] logging in python

[Teguh Iskanto]

Regardless of how bad the API was written, I have to say it does the job
well and the system is still running in production flawlessly up until now
(and yes it runs in a multi-threaded fashion). When making the choice of
which API should be used, I always try to balance between practicality and
theory (and the last thing of course which one is the best to get the job
done). The regression test will draw the line and prove if we're making the
right choice or not (or just mere making academic exercise)

Cheers,
Teguh Iskanto


On Fri, Feb 12, 2010 at 3:12 PM, Richard Jones <r1chardj0n3s at gmail.com>wrote:

> On 12/02/2010, at 3:00 PM, Teguh Iskanto wrote:
> > Try "logging" , for info : 'pydoc logging'
> > It comes as a default from python installation and it's a thread-safe
> module as I've used this in the production environment
>
> ... and it has possibly the worst API of any module in the standard library
> :)
>
> It's almost like it was written to slavishly follow an implementation from
> another language that doesn't have either a string formatting operator or
> decent built-in data structures for configuration ;)
>
> But yes, it is thread-safe.
>
>
>      Richard
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> http://mail.python.org/mailman/listinfo/melbourne-pug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20100212/473b89d6/attachment-0001.htm>