When mod_wsgi was young, I created various integration guides on how to use some of the main stream Python web applications and frameworks in conjunction with it. This was to make the path of moving to mod_wsgi somewhat easier, especially given that all those applications and frameworks didn't provide documentation of their own at the time.
Things have moved on since then, mod_wsgi has matured and most of those applications and frameworks provide their own documentation, although in some cases not very good. Even so, I simply do not have the time to keep up with developments on the various Python web applications and frameworks. I will therefore stop trying to maintain the majority of the existing integration guides and will instead remove them and refer to the documentation on the sites for the packages instead, along with pointers to mailing lists or IRC channels where you can get help for those packages. The integration guides that I will be deprecating and changing to link to site for that package are: http://code.google.com/p/modwsgi/wiki/IntegrationWithCherryPy http://code.google.com/p/modwsgi/wiki/IntegrationWithKarrigell http://code.google.com/p/modwsgi/wiki/IntegrationWithMoinMoin http://code.google.com/p/modwsgi/wiki/IntegrationWithPylons http://code.google.com/p/modwsgi/wiki/IntegrationWithTurboGears http://code.google.com/p/modwsgi/wiki/IntegrationWithWebPy So, in effect, I will only try and maintain guides for Django and Trac. The reason for retaining these is that they are the most popular in their class and I still need to maintain some to use as general guides to illustrate different configuration options. When I have the time, you can actually expect the integration guides for these packages to be updated and improved. I will be posting to appropriate mailing lists or groups for the packages for which integration guides are being deprecated giving them the warning, thus allowing them to integrate anything useful from those guides into their own documentation before the page content is removed. If you belong to any of those communities though, you might start the ball rolling and start that process. Since I will be moving to just a link to existing documentation for most packages, I will also start adding additional pages for other packages I don't already provide information about due to now having time, such as Werkzeug and others. Feel free to suggest other popular frameworks with a substantial user base that I could list. Hopefully people will not see this as a backward step. You really do need to appreciate how time consuming and draining it is keeping such information up to date and answering questions about integration with other packages. By doing this I hope to be able to get better focus on the core documentation which explains the underlying concepts of how to use mod_wsgi rather than wasting time on the peculiarities of how to get it working with a specific package, especially those which seem not to want to make it easy to host except through their preferred embedded web server. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
