On 20/10/2005, at 5:49 PM, Nicolas Lehuen wrote:
> And I agree with all these points except that I don't think it's
> trivial to get it right. In fact, that it is *not* trivial may be
best
> argument for inclusion in mod_python. Having everyone write
seemingly
> trivial logging code which causes mod_python memory leaks or
segfaults
> ultimately reflects poorly on mod_python, even if it's the user's
own
> bad code.
Absolutely. I would be +1 on including a module that handles logging
with all the management required for it to work properly in a
mod_python
context.
Regards,
That's my position, too. That's what I meant by "either we get it
thoroughly right, or we don't integrate it into mod_python".
If logging is going to be addressed, it may be worthwhile at the
same time looking at how sys.stdout/sys.stderr (especially the
latter) behave in the context of mod_python. This is because not
all modules use logging and instead use sys.stderr. Problem is
that sometimes there are issues with this being flushed out properly
and it only ends up appearing in the Apache log file when Apache
is shutdown. This can be confusing when debugging problems
as the messages don't appear in the log straight away.
Graham
