| Graham Dumpleton (JIRA) 2006-06-14, 7:12 am |
| [ http://issues.apache.org/jira/brows...action_12416169 ]
Graham Dumpleton commented on MODPYTHON-74:
-------------------------------------------
For the record and as I have mentioned on the mailing list:
http://mail-archives.apache.org/mod...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 whic
h 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_pyt
hon 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 mai
ling 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.
> Add a WSGI handler to support WSGI-based frameworks
> ---------------------------------------------------
>
> Key: MODPYTHON-74
> URL: http://issues.apache.org/jira/browse/MODPYTHON-74
> Project: mod_python
> Type: New Feature
> Components: core
> Reporter: Nicolas Lehuen
> Priority: Minor
> Fix For: 3.3
>
> There is a complete implementation here :
> http://www.amorhq.net/blogs/index.p..._for_mod_python
|