Re: Discuss https://github.com/django/django/pull/11157

_response(). That’s it. > > This was Tom’s point in his review four years ago: the ease of directly > implementing it means the added API surface area isn’t worth it. > > On Sat, 20 Jul 2019 at 13:31, Petr Glotov > > wrote: > >> What if we keep *StreamingTemplateR

Re: Discuss https://github.com/django/django/pull/11157

What if we keep *StreamingTemplateResponse* and do *TemplateView(stream=True) *flag? I just want to have something out of the box to use. On Friday, July 19, 2019 at 5:40:52 PM UTC-7, Petr Glotov wrote: > > Hi All, there is a PR <https://github.com/django/django/pull/11157> where

Discuss https://github.com/django/django/pull/11157

Hi All, there is a PR where template streaming is introduced, and recently a discussion emerged on wether a *StreamingTemplateView* class belongs in Django. I know for sure I'd be glad to replace *TemlateView *based views in one of project I'm worki

PR review request https://github.com/django/django/pull/11157

Not sure if posting review requests to mailing list is part of the process, but could we get https://github.com/django/django/pull/11157 reviewed/merged? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To