Nicolas Lehuen <[EMAIL PROTECTED]> writes: > In that case, setting up the logging handler should be done by the user, > making sure that it is set up only once per interpreter, even in the context > of a multi-threaded MPM. It's not a trivial thing ; looks like this is a job > for PythonImport.
Hang on. I did NOT ask for mod_python to be altered to set up any logging handler. All that I asked is that a module similar to mine be included in mod_python's dist so that it can be available to programmers by default. > So my advice is that if the set up is done by the user, then the logging > handler should be considered as contrib. If you provide a way for mod_python > to directly set up the handler, maybe this could be considered part of > mod_python. I've been using mod_python (via Debian) for a while and I don't know anything about a contrib directory. I presume therefore that it isn't distributed with the package which is what I am arguing against. Here's a precis of my argument: - logging is such a common thing for many projects; - python has an official logging API; - Apache has a logging system that most people using python logging will want to interface to - code to allow python logging and Aapache logging to be glued together is trivial - if everyone has to write trivial logging code over and over again that's a bad thing I am NOT asking the mod_python people to spec any wildly strange code I am NOT asking for mod_python to be altered, except in terms of the files that are distributed with it I am NOT even asking that the maintainers take on new code (I'll happily maintain it and do whatever needs to be done to import it into your code base)... Sheesh guys. This seemed like a no brainer to me. Nic
