Fix missing CSRF exemption on viewsets

Clarify "raised inside REST framework"

DefaultRouter support for viewsets without an implemented default action

Update authtoken latest Django 1.7 migration

I ran into an issue today where I was not seeing the rest_framework.views.exception_handler do what I thought it should be doing. It turned out that I had imported View from rest_framework.views rather than importing APIView from rest_framework.views. The phrase "raised inside REST framework" was confusing as I was debugging this issue. I was unsure if that meant that I could raise those exceptions in my code or if it had to originate from within framework code.

I'm not sure if the proposed wording is ideal, I just wanted to point out what I found to be confusing.

add wq.db router and django-rest-pandas renderers

Add Third Party Resources Topic section

Added DefaultRouter support (and test) for viewsets without the default action implemented, which is usually the list action.

Fix grammar in login error message

add django rest pandas

Make sure APIRoot.get can take on args, kwargs so router can be embedded...

Fixed #1533 - Resolved issue with integer keys on nested choices never v...

Fixing quotes in filtering.md example code.

Stop the API Client converting empty lists/dicts to empty strings

Incorrect quotes used in examples.

Try running Tox from Travis

- Added unit test for nested `choices` argument.
- Added unit test for non-nested `choices` argument.

Better mapping for custom model fields to serializer fields.

Support RFC6266 encoded filenames

Supported translated text view descriptions