Nick wrote:
As a long time user of mod_python, I would add that I personally disagree with including Sessions, psp, publisher, etc. in the base distribution, since these things seem to have held up releases. I don't use any of those things as all with mod_python, and I don't see how they're necessary to use mod_python for what it's for: creating apache extension modules in Python.
I agree, and my usage is the exact opposite of Nick's. I use mod_python exclusively with Publisher, and even I think it's odd to include it. With a stable base distribution and a repository of supported handlers, it may not be necessary to touch the core if you're simply trying to address an issue in a handler.
But there needs to be something. What do you see on the list all the time? People asking how do I implement database pooling, how to I use sessions, here's my database implementation for sessions. I say put the publisher there as well, since it doesn't have anything to do with the philosophy of mod_python, even by Grisha's definition, and solves some release issues with mod_python itself (can anyone say imports?).
It also gives handler writers an incentive to contribute code to the core without having to study the impact on other handlers included in the main distribution. If it raises issues, handler maintainers will have an opportunity to voice their concerns or adapt.
