James Gardner wrote:
Ian Bicking wrote:
Another thing I noticed when writing the error handler is that if an
application or middleware component doesn't form a header or set the
status correctly it can be tricky to track down where the error
occurred. If the application used a special object for
Ian Bicking wrote:
Another thing I noticed when writing the error handler is that if an
application or middleware component doesn't form a header or set the
status correctly it can be tricky to track down where the error
occurred. If the application used a special object for headers and
status
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
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
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
