From fdcef1b86359b1c658b58fdfc6bfdebc11f830f6 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 17 Sep 2014 08:37:27 -0400 Subject: [PATCH] [1.7.x] Fixed #23491 -- Clarified tutorial 3. Thanks diek for the suggestion. Backport of 54fd84e432 from master --- docs/intro/tutorial03.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/intro/tutorial03.txt b/docs/intro/tutorial03.txt index d94bca084a..c989ee0d1f 100644 --- a/docs/intro/tutorial03.txt +++ b/docs/intro/tutorial03.txt @@ -287,7 +287,7 @@ you want, using whatever Python libraries you want. All Django wants is that :class:`~django.http.HttpResponse`. Or an exception. Because it's convenient, let's use Django's own database API, which we covered -in :doc:`Tutorial 1 `. Here's one stab at the ``index()`` +in :doc:`Tutorial 1 `. Here's one stab at a new ``index()`` view, which displays the latest 5 poll questions in the system, separated by commas, according to publication date: @@ -304,6 +304,8 @@ commas, according to publication date: output = ', '.join([p.question_text for p in latest_question_list]) return HttpResponse(output) + # Leave the rest of the views (detail, results, vote) unchanged + There's a problem here, though: the page's design is hard-coded in the view. If you want to change the way the page looks, you'll have to edit this Python code. So let's use Django's template system to separate the design from Python by