From 1c989f59d4ec2c4926a809c82a2cc9e8128b03d3 Mon Sep 17 00:00:00 2001
From: Joseph Kocherhans <joseph@jkocherhans.com>
Date: Wed, 11 Jan 2006 21:46:50 +0000
Subject: [PATCH] magic-removal: Updated docs to reflect new location of
 django.utils.httpwrappers

git-svn-id: http://code.djangoproject.com/svn/django/branches/magic-removal@1916 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/authentication.txt   | 2 +-
 docs/forms.txt            | 2 +-
 docs/outputting_csv.txt   | 4 ++--
 docs/outputting_pdf.txt   | 2 +-
 docs/request_response.txt | 6 +++---
 docs/tutorial03.txt       | 6 +++---
 6 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/authentication.txt b/docs/authentication.txt
index 46a76b853c..2a7076ff78 100644
--- a/docs/authentication.txt
+++ b/docs/authentication.txt
@@ -237,7 +237,7 @@ The raw way
 The simple, raw way to limit access to pages is to check
 ``request.user.is_anonymous()`` and either redirect to a login page::
 
-    from django.utils.httpwrappers import HttpResponseRedirect
+    from django.http import HttpResponseRedirect
 
     def my_view(request):
         if request.user.is_anonymous():
diff --git a/docs/forms.txt b/docs/forms.txt
index cf51d1bdcf..d7d3dd7c5f 100644
--- a/docs/forms.txt
+++ b/docs/forms.txt
@@ -67,7 +67,7 @@ POSTed data from the browser and creates a new ``Place`` object::
 
     from django.core.exceptions import Http404
     from django.core.extensions import render_to_response
-    from django.utils.httpwrappers import HttpResponse, HttpResponseRedirect
+    from django.http import HttpResponse, HttpResponseRedirect
     from django.models.places import places
     from django.core import formfields
 
diff --git a/docs/outputting_csv.txt b/docs/outputting_csv.txt
index 3f95b3600d..326f1bd61b 100644
--- a/docs/outputting_csv.txt
+++ b/docs/outputting_csv.txt
@@ -30,7 +30,7 @@ and Django's ``HttpResponse`` objects are file-like objects.
 Here's an example::
 
     import csv
-    from django.utils.httpwrappers import HttpResponse
+    from django.http import HttpResponse
 
     def some_view(request):
         # Create the HttpResponse object with the appropriate CSV header.
@@ -79,7 +79,7 @@ template output the commas in a ``{% for %}`` loop.
 
 Here's an example, which generates the same CSV file as above::
 
-    from django.utils.httpwrappers import HttpResponse
+    from django.http import HttpResponse
     from django.core.template import loader, Context
 
     def some_view(request):
diff --git a/docs/outputting_pdf.txt b/docs/outputting_pdf.txt
index bd209b2e90..3b7d6b0909 100644
--- a/docs/outputting_pdf.txt
+++ b/docs/outputting_pdf.txt
@@ -47,7 +47,7 @@ objects.
 Here's a "Hello World" example::
 
     from reportlab.pdfgen import canvas
-    from django.utils.httpwrappers import HttpResponse
+    from django.http import HttpResponse
 
     def some_view(request):
         # Create the HttpResponse object with the appropriate PDF headers.
diff --git a/docs/request_response.txt b/docs/request_response.txt
index 818c639d9a..13de013b6c 100644
--- a/docs/request_response.txt
+++ b/docs/request_response.txt
@@ -131,7 +131,7 @@ QueryDict objects
 -----------------
 
 In an ``HttpRequest`` object, the ``GET`` and ``POST`` attributes are instances
-of ``django.utils.httpwrappers.QueryDict``. ``QueryDict`` is a dictionary-like
+of ``django.http.QueryDict``. ``QueryDict`` is a dictionary-like
 class customized to deal with multiple values for the same key. This is
 necessary because some HTML form elements, notably ``<select multiple>``, pass
 multiple values for the same key.
@@ -269,7 +269,7 @@ In contrast to ``HttpRequest`` objects, which are created automatically by
 Django, ``HttpResponse`` objects are your responsibility. Each view you write
 is responsible for instantiating, populating and returning an ``HttpResponse``.
 
-The ``HttpResponse`` class lives at ``django.utils.httpwrappers.HttpResponse``.
+The ``HttpResponse`` class lives at ``django.http.HttpResponse``.
 
 Usage
 -----
@@ -351,7 +351,7 @@ HttpResponse subclasses
 
 Django includes a number of ``HttpResponse`` subclasses that handle different
 types of HTTP responses. Like ``HttpResponse``, these subclasses live in
-``django.utils.httpwrappers``.
+``django.http``.
 
 ``HttpResponseRedirect``
     The constructor takes a single argument -- the path to redirect to. This
diff --git a/docs/tutorial03.txt b/docs/tutorial03.txt
index c5367270ab..58c5ece244 100644
--- a/docs/tutorial03.txt
+++ b/docs/tutorial03.txt
@@ -148,7 +148,7 @@ haven't written any views yet).
 Time to write the first view. Open the file ``myproject/polls/views.py``
 and put the following Python code in it::
 
-    from django.utils.httpwrappers import HttpResponse
+    from django.http import HttpResponse
 
     def index(request):
         return HttpResponse("Hello, world. You're at the poll index.")
@@ -186,7 +186,7 @@ latest 5 poll questions in the system, separated by commas, according to
 publication date::
 
     from django.models.polls import polls
-    from django.utils.httpwrappers import HttpResponse
+    from django.http import HttpResponse
 
     def index(request):
         latest_poll_list = polls.get_list(order_by=['-pub_date'], limit=5)
@@ -199,7 +199,7 @@ So let's use Django's template system to separate the design from Python::
 
     from django.core.template import Context, loader
     from django.models.polls import polls
-    from django.utils.httpwrappers import HttpResponse
+    from django.http import HttpResponse
 
     def index(request):
         latest_poll_list = polls.get_list(order_by=['-pub_date'], limit=5)