  :attr:`HttpResponse.content` attribute before the response is returned.
  
  .. versionchanged:: 1.5
  
  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.
  
 
</s> remove 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.
 </s> add     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. </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 In Python 3, the logic is reversed, that is normal strings are Unicode, and
when you want to specifically create a bytestring, you have to prefix the
string with a 'b'. As we are doing in Django code from version 1.5,
we recommend that you import ``unicode_literals`` from the __future__ library
in your code. Then, when you specifically want to create a bytestring literal,
prefix the string with 'b'.
 </s> add     In Python 3, the logic is reversed, that is normal strings are Unicode, and
    when you want to specifically create a bytestring, you have to prefix the
    string with a 'b'. As we are doing in Django code from version 1.5,
    we recommend that you import ``unicode_literals`` from the __future__ library
    in your code. Then, when you specifically want to create a bytestring literal,
    prefix the string with 'b'. </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. </s> remove             The ``content_type`` attribute was added.
 </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.
  :attr:`HttpResponse.content` attribute before the response is returned.
  
  .. versionchanged:: 1.5
  
    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.
    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.
    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.
  
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