Re: [Web-SIG] wsgi write=start_response() and iterable return?

> From: Aaron Watters > > If an application returns an iterable response and *also* > calls the write()... what is supposed to happen?  After carefully considering all the responses on this issue ;c) I came up with the following strategy for dealing with calls to write() in combination with

Re: [Web-SIG] wsgi write=start_response() and iterable return?

At 08:42 AM 1/4/2010 -0800, Aaron Watters wrote: > From: Aaron Watters > > If an application returns an iterable response and *also* > calls the write()... what is supposed to happen? After carefully considering all the responses on this issue ;c) I came up with the following strategy for

[Web-SIG] wsgiorg.routing_path addition to the wsgiorg.routing_args Specification

Hello everybody. The current wsgiorg.routing_args specification requires that "Portions of the path that have been parsed should still be moved to SCRIPT_NAME (and removed from PATH_INFO)", but: 1.- That's against semantics. According to PEP 333 and the CGI spec, SCRIPT_NAME and PATH_INFO mus