I hope that if the author wants to resurrect it, he'll consider creating a new mod_python focused exclusively on the new Python. Position it that way. Make it Python 3.4 or later with no support for anything earlier so that all effort can focus on creating the world's best support for the next generation of Python web apps.
Just a thought.
The project is already being worked on and support for Py3 is implemented. He's reaching out looking for people to help him test it.
Any resources (time, attention, research, answering user questions, design simplicity, ...) that are expended in an effort to support pre-3.4 versions and users are resources that could be turned instead to the challenge of making the 3.4+ product even better.
With this approach, he could potentially, gradually, change the market's mindset from "mod_python is dead, use mod_wsgi" to "if you're still stuck with Py2, you'll have to use mod_wsgi, but if you are starting a new project, you should go with mod_python."
It is, of course, his choice, but I'm suggesting that there is an alternative where all available resources are focused on the future, benefiting new projects at the expense of whatever remains of the legacy, going for strongest ultimate interest even at the possibility that it might not produce the strongest initial interest, and attempting to own the mindshare of "best system for new Python projects" by positioning itself exclusively as that, not positioning new Python project support a recent add-on to an old, legacy technology.
It's a matter of choosing market, positioning, and resource allocation, and I'm pointing out how, with a certain choice, the market perception that "mod_python is dead" doesn't have to be a problem and could even have advantages.
Hear, Hear! As much as I think Agile is an improvement over more misused software development models, I still prefer working on my own time at my own pace the best.
Very excellent story.
Measure your velocity to predict delivery times.
Not push yourself to hit required (i.e. hoped for) delivery.
I am certainly interested in how the Python community will react to the mod_python revival.
(It hasn't been long since we've added nodejs support, but that community has shown a lot more love already)
Unless ofcourse you are using it together with other nginx modules, that's an unfortunate effect of nginx's module architecture I'm afraid.
But I also feel sorry for all the people who have struggled to do normal things with mod_python, often just because they assumed it was the default due to its name, and did not know that it got left behind by the rest of the world. This is why people say "mod_python is dead," to save others the pointless struggle typically encountered while trying to do the typical things with mod_python. And it's not only the long period without maintenance or the weak documentation. The whole ecosystem just moved on. It's been many years.
The reason it is you against the world today is that you want everyone to drop WSGI to use mod_python. Maybe this was possible in 2003-2005 or so. But for a long time now, mod_python is just not a good alternative to WSGI and all the tools that use it, even if it is good in its own ways. Trying to replace WSGI with mod_python today doesn't make sense. Please give up the goal of replacing WSGI with mod_python and take a new direction!
The only thing I wanted was a simple means to pass around input that I didn't have to write by hand... much to the contrary of mod_python's intent.
I am glad Grisha is working on it again, though. I am always pleased to see labors of love for 20 years get sustained attention.
Anyway, thank-you for your enormous contribution to Python on the web, Graham. And if it was his shoulders you stood on, my thanks to Grisha too.
And without support for reloading, that pretty much guarantees who'll be using it.