Istvan Albert wrote: >suppose one wants to return content created by two generators ... they >could wrap it themselves into a single one but why not write it both to >the response and let that iterate thru each, > > What if they want three? :-). I should say that it's still looking theoretical, sorry! :-)
I don't want to turn response into a generator multiplexor. Its goal is just accept some iterable content and relay it to network. Accepting content in constructor and write interface are two separate ways to do this. Allowing both ways of content creation simultaneously just will make whole interaction model complicated and less obvious (imho). >if your code would support that it would end up being simpler, with no >special casing for strings ... win-win situation > > Special casing will go away, yes. But then HttpResponse should handle two iterators by itself. Which means keeping them both and writing a separate generator function walking them one-by-one. This is not really simpler than just a single boolean (imho, again). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
