magic-removal: Moved session middleware from django/middleware/sessions.py to django/contrib/sessions/middleware.py

git-svn-id: http://code.djangoproject.com/svn/django/branches/magic-removal@1866 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/middleware.txt

@@ -95,7 +95,7 @@ Handles conditional GET operations. If the response has a ``ETag`` or
 Also removes the content from any response to a HEAD request and sets the
 ``Date`` and ``Content-Length`` response-headers.
 
-django.middleware.sessions.SessionMiddleware
+django.contrib.sessions.middleware.SessionMiddleware
 --------------------------------------------
 
 Enables session support. See the `session documentation`_.
@@ -176,8 +176,8 @@ Guidelines
       to it.
 
     * Feel free to look at Django's available middleware for examples. The
-      default Django middleware classes are in ``django/middleware/`` in the
-      Django distribution.
+      core Django middleware classes are in ``django/middleware/`` in the
+      Django distribution. The session middleware is in ``django/contrib/sessions``.
 
     * If you write a middleware component that you think would be useful to
       other people, contribute to the community! Let us know, and we'll

docs/sessions.txt

@@ -14,7 +14,7 @@ Session functionality is enabled by default.
 
 You can turn session functionality on and off by editing the
 ``MIDDLEWARE_CLASSES`` setting. To activate sessions, make sure
-``MIDDLEWARE_CLASSES`` contains ``"django.middleware.sessions.SessionMiddleware"``.
+``MIDDLEWARE_CLASSES`` contains ``"django.contrib.sessions.middleware.SessionMiddleware"``.
 
 If you don't want to use sessions, you might as well remove the
 ``SessionMiddleware`` line from ``MIDDLEWARE_CLASSES``. It'll save you a small