[melbourne-pug] logging in python

[James Alford]

I ended up using the logging from the python install.

I have to agree on both points but I like the end result.

Its nice to see it logging from threads with no problems (yet), if
lumberjack was stable then I would have looked into it.

On Fri, Feb 12, 2010 at 3:34 PM, Teguh Iskanto <tiskanto at gmail.com> wrote:
> 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
>
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> http://mail.python.org/mailman/listinfo/melbourne-pug
>
>