Istvan Albert wrote: >but it is not an arbitraty iterator one is writing to, it is the the >HttpResponse, why couldn't it handle new content being added just >because some content is present as an interator? once it exhausts the >original iterator it could continue on (if new content was added after >it) > > I just can't imagine any practical application of this... This is why there is a "hard-coded" exception: to prevent thing that is technically possible but doesn't make sense.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---