On Nov 11, 10:28 am, "Aaron Swartz" <[EMAIL PROTECTED]> wrote:
> > never being called. Do I have to call this explicitly in my view
> > functions somewhere or is web.py supposed to take care of that for me?
>
> That's odd. web.py is supposed to take care of it for you. Indeed,
> without calling start_response no pages would ever get returned to the
> server, so it must be calling something's start_response. What version
> of web.py are you running?
Sorry, that was a vital stat. ;) I'm using web.py 0.23 on an i686 Arch
Linux system running python2.6.
I've put print statements in gzip_start_response and they never get
output; however maybe the output is being captured by web.py. Since
the middleware wraps web.py, I assumed web.debug wouldn't work here.
What do you think?
Thanks again,
Dusty
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
