> S4. An I/O error (such as Connection reset by peer or > Broken pipe) > occurs when writing to the write() callable returned by > start_response().
Interesting. I had totally missed the write() callable return value required by start_response. If an application returns an iterable response and *also* calls the write()... what is supposed to happen? Yikes. This may require some careful adjustments to WHIFF. I had run into this and hacked around it on an ad hoc basis assuming it was a mistake. -- Aaron Watters === less is more _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
