  This technique is fragile and was deprecated in Django 1.5. If you need the
  response to be streamed from the iterator to the client, you should use the
  :class:`StreamingHttpResponse` class instead.
  
  As of Django 1.7, when :class:`HttpResponse` is instantiated with an
  iterator, it will consume it immediately, store the response content as a
  string, and discard the iterator.
  
  .. versionchanged:: 1.5
  
  You can now use :class:`HttpResponse` as a file-like object even if it was
  instantiated with an iterator. Django will consume and save the content of
 
</s> remove This technique is fragile and was deprecated in Django 1.5. If you need the
response to be streamed from the iterator to the client, you should use the
:class:`StreamingHttpResponse` class instead.
 </s> add     This technique is fragile and was deprecated in Django 1.5. If you need the
    response to be streamed from the iterator to the client, you should use the
    :class:`StreamingHttpResponse` class instead. </s> remove You can now use :class:`HttpResponse` as a file-like object even if it was
instantiated with an iterator. Django will consume and save the content of
the iterator on first access.
 </s> add     You can now use :class:`HttpResponse` as a file-like object even if it was
    instantiated with an iterator. Django will consume and save the content of
    the iterator on first access. </s> remove             The ``content_type`` attribute was added.
 </s> add  </s> remove Some fields in a model won't be deferred, even if you ask for them. You can
never defer the loading of the primary key. If you are using
:meth:`select_related()` to retrieve related models, you shouldn't defer the
loading of the field that connects from the primary model to the related
one, doing so will result in an error.
 </s> add     Some fields in a model won't be deferred, even if you ask for them. You can
    never defer the loading of the primary key. If you are using
    :meth:`select_related()` to retrieve related models, you shouldn't defer the
    loading of the field that connects from the primary model to the related
    one, doing so will result in an error. </s> remove When the :func:`atomic` decorator is nested, it creates a savepoint to allow
partial commit or rollback. You're strongly encouraged to use :func:`atomic`
rather than the functions described below, but they're still part of the
public API, and there's no plan to deprecate them.
 </s> add     When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them.
    As of Django 1.7, when :class:`HttpResponse` is instantiated with an
    iterator, it will consume it immediately, store the response content as a
    string, and discard the iterator.
  This technique is fragile and was deprecated in Django 1.5. If you need the
  response to be streamed from the iterator to the client, you should use the
  :class:`StreamingHttpResponse` class instead.
  
    As of Django 1.7, when :class:`HttpResponse` is instantiated with an
    iterator, it will consume it immediately, store the response content as a
    string, and discard the iterator.
    As of Django 1.7, when :class:`HttpResponse` is instantiated with an
    iterator, it will consume it immediately, store the response content as a
    string, and discard the iterator.
    As of Django 1.7, when :class:`HttpResponse` is instantiated with an
    iterator, it will consume it immediately, store the response content as a
    string, and discard the iterator.
  
  .. versionchanged:: 1.5
  
  You can now use :class:`HttpResponse` as a file-like object even if it was
  instantiated with an iterator. Django will consume and save the content of
keep keep keep keep replace replace replace keep keep keep keep keep
 Adapted uses of versionchanged/versionadded to the new form.

Refs #20104. 
docs/ref/request-response.txt