James Gardner wrote:
Ian Bicking wrote:
web.wsgi.error: one standard I'd like for middleware would be some key
you could set that would indicate that some error handler exists, and
applications further down the stack shouldn't catch unexpected
exceptions (of course expected exceptions are a diff
What do people think about collaborating on a kind of "standard" library
of WSGI middleware? (Not standard like distributed-with-Python, just
well publicized.) This is what I've tried to put together a little with
WSGIKit, though not all parts of it would apply. And other people are,
I think
Ian Bicking wrote:
web.wsgi.error: one standard I'd like for middleware would be some key
you could set that would indicate that some error handler exists, and
applications further down the stack shouldn't catch unexpected
exceptions (of course expected exceptions are a different matter).
Then
James Gardner wrote:
Hello All,
I'd like to announce the release of the Python Web Modules 0.5.0.
This development release brings WSGI support to the modules.
* Web Server Gateway Interface support - auth, error, database and session
middleware and a WSGI Server.
Cool, good to see more of this ki
Titus Brown wrote:
Hi all,
I sat down today to hack out a simple commenting system for HTML
articles, and ended up using WSGI to implement a pipe-style solution.
You can see the results at
http://www.idyll.org/~t/articles.cgi/
This CGI script serves HTML files from a directory hierarchy. A
Hello All,
I'd like to announce the release of the Python Web Modules 0.5.0.
This development release brings WSGI support to the modules.
* Web Server Gateway Interface support - auth, error, database and session
middleware and a WSGI Server.
* Licensed under the LGPL after discussions on the mai
