You mean we'll be able to do the following?
class bla:
def GET(self):
yield "hello"
yield "world"
because that's very cool.
On Feb 8, 11:00 am, "Anand Chitipothu" <[EMAIL PROTECTED]> wrote:
> On Feb 8, 2008 1:40 PM, mint <[EMAIL PROTECTED]> wrote:
>
>
>
> > The roadmap for web.py describes moving from print to return for
> > version 0.3. This is an architectural mistake. With print you can
> > stream the response back to client. You don't need to formulate the
> > entire response in memory before sending it back. By switching to
> > return we will be forced to generate the entire response before
> > starting to send it back to the client. For your average case this
> > won't matter but when returning large datasets this change will force
> > you to build up the entire response in memory. When python allowed
> > generator expressions it suddenly allowed pythonic iteration without
> > the in memory tax that list comprehensions required. The switch to
> > return is in effect moving from generator expression back to list
> > comprehensions for web.py. I don't want to move back.
>
> > I say vote no on the switch to return.
>
> You can use yield if you want that behavior.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
