On Sat, Apr 27, 2013 at 1:24 AM, Graham Dumpleton
graham.dumple...@gmail.com wrote:
I described a different way of doing WSGI which would better cope with post
response hooks at the Python Web Summit at PyCon in 2012. It made use of the
context manager abstraction so it wouldn't screw with the
Hi,
Newbie opinion here.
Since we are talking about Tulip and PEP 3156, I think it's high time we
address some of the design flaws in WSGI 1.0
One major problem with WSGI is that it can not handle true post-response
hooks.
The closest hack I found is this:
Hi Luca,
Unfortunately I haven't thought yet about the interactions between WSGI and
Tulip or PEP 3156. While I am pretty familiar with WSGI, I have never used
its async features, so I can't be much of a help. My best guess is that we
won't make any changes to WSGI to support PEP 3156 in Python
