|
For the record and as I have mentioned on the mailing list:
http://mail-archives.apache.org/mod_mbox/httpd-python-dev/200606.mbox/%3c058832EE-FD45-4749-BB68-5D79BD154B4D@dscpl.com.au%3e I don't believe that a mod_python.wsgi should be added to mod_python core package. The primary reason is even if that is done, people will still keep asking where they can get a copy of it which will work with older versions of mod_python from 2.7 through 3.2. Further, changes to it will be dependent on release cycles of mod_python which at the moment are infrequent. The latter would be an issue where people expect new wsgi optional component layers to be added based on how wsgi is evolving and in general if problems need to be fixed. Finally, it is an extra burden that the core mod_python developers don't need, there being enough to do already. What is needed is for someone distinct from the current mod_python developers to really take onwnership of it and create a project for it on SourceForge or elsewhere. Actual discussion of development and maintenance can still be done on the mod_python mailing lists and I am sure current mod_python developers/users would freely contribute ideas on how to implement it the best way. Most importantly, if a separate project, it can be made to work for and be available for any version of mod_python and not be constrained by release cycles of mod_python. That it will work for all versions of mod_python would be important as it will make it most widely portable. |
||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Minor
Add a WSGI handler to support WSGI-based frameworks
I know some of the mod_python developers don't quite like WSGI but consider that today there are not much exlusively mod_python applications (and some people need/want to use web servers other than Apache).
This means that, current applications can't depend on mod_python features, but most often they don't even need the special mod_python features.
Current applications also implement special glue code to use the app with mod_python, scgi, cgi etc.. In the future, applications developers would want to avoid that, and you can see that almost all of the new web-app development is based on WSGI. You can even run Zope in a WSGI server (I wonder if anyone tried to do it in mod_python/WSGI).
Including modpython_gateway (possibly as mod_python.wsgi) in the mod_python distribution will make mod_python an easy choice for serving WSGI applications without the need to hunt down mod_python WSGI implementations.
Also I'd suggest that some features are implemented in modpython_gateway:
- sendfile support (http://www.python.org/dev/peps/pep-0333/#optional-platform-specific-file-handling)
- more robust PATH_INFO and SCRIPT_NAME detection, possibly without the "PythonOption SCRIPT_NAME" hack.... well, I think this might not be possible but it would be great if is.