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 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 -~----------~----~----~----~------~----~------~--~---
