Nic, there is something I need to understand before giving my advice on the subject. I'm not familiar with the logging API, can you tell me how you configure Python to use this logging implementation ? Looks like we have to manipulate configuration object, set up handlers and so on... If so I guess we'd have to add a word or two in the documentation on the best way to do this in the mod_python context...

Regards,
Nicolas

2005/10/19, Nic Ferrier <[EMAIL PROTECTED]>:

Nic Ferrier wrote:
>> I really think the argument about mod_python being minimal does not
>> apply here.
>>
>> Nick said it - mod_python is glue between Python and apache - well,
>> making Python logging work directly to Apache seems like important
>> glue to me.

Nick <[EMAIL PROTECTED]> writes:

> And again I renew my argument that there needs to be some kind of
> contrib archive that is probably separate from mod_python and
> unsupported in the core distribution.  Maybe a wiki or code repository
> or something to support all the contributions like this.  That way all
> these neat things can be available to people who are using mod_python,
> but not burden the development process of mod_python itself with issues
> concerning the constributions.

I agree. But I don't think logging glue should go in it. logging glue
should be in core mod_python because it is glue, not a feature built
on top of Apache or Python, simply a link between the two worlds.

If logging is just available in an addon then developers have still
got the problem of deploying mod_python PLUS pretty much essential
stuff from so and so archive as well as the app.


Nic

Reply via email to