  """
  The :mod:`response` module provides Response classes you can use in your
  views to return a certain HTTP response. Typically a response is *rendered*
  into a HTTP response depending on what renderers are set on your view and
  als depending on the accept header of the request.
  """
  
  from django.template.response import SimpleTemplateResponse
  from django.core.handlers.wsgi import STATUS_CODE_TEXT
  
 
</s> remove         Should be a tuple/list of classes as described in the :mod:`renderers` module.
 </s> add         `renderers` is a list/tuple of renderer instances and represents the set of renderers
        that the response can handle. </s> remove     Adds behavior for pluggable `Renderers` to a :class:`views.View` class.
 </s> add     Adds behavior for pluggable `renderers` to a :class:`views.View` class. </s> remove from djangorestframework.response import ErrorResponse
 </s> add from djangorestframework.response import ImmediateResponse </s> remove         content is the raw content.

        The set of renderers that the response can handle.
 </s> add         `content` is the raw content, not yet serialized. This must be simple Python
        data that renderers can handle (cf: dict, str, ...) </s> remove     renderers = renderers.DEFAULT_RENDERERS
 </s> add     renderer_classes = renderers.DEFAULT_RENDERERS
The :mod:`response` module provides :class:`Response` and :class:`ImmediateResponse` classes.

`Response` is a subclass of `HttpResponse`, and can be similarly instantiated and returned
from any view. It is a bit smarter than Django's `HttpResponse` though, for it knows how
to use :mod:`renderers` to automatically render its content to a serial format.
This is achieved by :

    - determining the accepted types by checking for an overload or an `Accept` header in the request
    - looking for a suitable renderer and using it on the content given at instantiation


`ImmediateResponse` is an exception that inherits from `Response`. It can be used
to abort the request handling (i.e. ``View.get``, ``View.put``, ...), 
and immediately returning a response.
  """
The :mod:`response` module provides :class:`Response` and :class:`ImmediateResponse` classes.

`Response` is a subclass of `HttpResponse`, and can be similarly instantiated and returned
from any view. It is a bit smarter than Django's `HttpResponse` though, for it knows how
to use :mod:`renderers` to automatically render its content to a serial format.
This is achieved by :

    - determining the accepted types by checking for an overload or an `Accept` header in the request
    - looking for a suitable renderer and using it on the content given at instantiation


`ImmediateResponse` is an exception that inherits from `Response`. It can be used
to abort the request handling (i.e. ``View.get``, ``View.put``, ...), 
and immediately returning a response.
The :mod:`response` module provides :class:`Response` and :class:`ImmediateResponse` classes.

`Response` is a subclass of `HttpResponse`, and can be similarly instantiated and returned
from any view. It is a bit smarter than Django's `HttpResponse` though, for it knows how
to use :mod:`renderers` to automatically render its content to a serial format.
This is achieved by :

    - determining the accepted types by checking for an overload or an `Accept` header in the request
    - looking for a suitable renderer and using it on the content given at instantiation


`ImmediateResponse` is an exception that inherits from `Response`. It can be used
to abort the request handling (i.e. ``View.get``, ``View.put``, ...), 
and immediately returning a response.
The :mod:`response` module provides :class:`Response` and :class:`ImmediateResponse` classes.

`Response` is a subclass of `HttpResponse`, and can be similarly instantiated and returned
from any view. It is a bit smarter than Django's `HttpResponse` though, for it knows how
to use :mod:`renderers` to automatically render its content to a serial format.
This is achieved by :

    - determining the accepted types by checking for an overload or an `Accept` header in the request
    - looking for a suitable renderer and using it on the content given at instantiation


`ImmediateResponse` is an exception that inherits from `Response`. It can be used
to abort the request handling (i.e. ``View.get``, ``View.put``, ...), 
and immediately returning a response.
The :mod:`response` module provides :class:`Response` and :class:`ImmediateResponse` classes.

`Response` is a subclass of `HttpResponse`, and can be similarly instantiated and returned
from any view. It is a bit smarter than Django's `HttpResponse` though, for it knows how
to use :mod:`renderers` to automatically render its content to a serial format.
This is achieved by :

    - determining the accepted types by checking for an overload or an `Accept` header in the request
    - looking for a suitable renderer and using it on the content given at instantiation


`ImmediateResponse` is an exception that inherits from `Response`. It can be used
to abort the request handling (i.e. ``View.get``, ``View.put``, ...), 
and immediately returning a response.
  """
  
  from django.template.response import SimpleTemplateResponse
  from django.core.handlers.wsgi import STATUS_CODE_TEXT
  
keep replace replace replace replace keep keep keep keep keep
 cleaned a bit Response/ResponseMixin code, added some documentation + renamed ErrorResponse to ImmediateResponse 
djangorestframework/response.py