  Basic building blocks for generic class based views.
  
  We don't bind behaviour to http method handlers yet,
  which allows mixin classes to be composed in interesting ways.
  
  Eg. Use mixins to build a Resource class, and have a Router class
      perform the binding of http methods to actions for us.
  """
  from django.http import Http404
  from rest_framework import status
  from rest_framework.response import Response
  
 
</s> remove         self.assertEquals(response.status_code, status.HTTP_200_OK)
 </s> add         self.assertEquals(response.status_code, status.HTTP_201_CREATED) </s> remove             return Response(serializer.data)
 </s> add             return Response(serializer.data, status=success_status) </s> remove         self.assertEquals(response.status_code, status.HTTP_200_OK)
 </s> add         self.assertEquals(response.status_code, status.HTTP_201_CREATED) </s> remove         self.assertEquals(response.status_code, status.HTTP_200_OK)
 </s> add         self.assertEquals(response.status_code, status.HTTP_201_CREATED)
  Basic building blocks for generic class based views.
  
  We don't bind behaviour to http method handlers yet,
  which allows mixin classes to be composed in interesting ways.



  """
  from django.http import Http404
  from rest_framework import status
  from rest_framework.response import Response
  
keep keep keep keep replace replace replace keep keep keep keep keep
 PUT as create should return 201.  Fixes #340. 
rest_framework/mixins.py