aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGil Gonçalves2014-11-20 11:33:42 +0000
committerGil Gonçalves2014-11-20 11:33:42 +0000
commit04d2635b24f0699ed8ed24436a58c203ad6a9a11 (patch)
treea0319ba8cbaa472307e81b85763bfec701ecb2b7
parent9b4757b7af3430fb8649a144afa047fbb3ca107b (diff)
downloaddjango-rest-framework-04d2635b24f0699ed8ed24436a58c203ad6a9a11.tar.bz2
Removed unused import from code snippet in tutorial
-rw-r--r--docs/tutorial/5-relationships-and-hyperlinked-apis.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/tutorial/5-relationships-and-hyperlinked-apis.md b/docs/tutorial/5-relationships-and-hyperlinked-apis.md
index 36473ce9..50552616 100644
--- a/docs/tutorial/5-relationships-and-hyperlinked-apis.md
+++ b/docs/tutorial/5-relationships-and-hyperlinked-apis.md
@@ -6,7 +6,6 @@ At the moment relationships within our API are represented by using primary keys
Right now we have endpoints for 'snippets' and 'users', but we don't have a single entry point to our API. To create one, we'll use a regular function-based view and the `@api_view` decorator we introduced earlier. In your `snippets/views.py` add:
- from rest_framework import renderers
from rest_framework.decorators import api_view
from rest_framework.response import Response
from rest_framework.reverse import reverse