From cbd90455a08c6ec379ec647415fc96c21ef39834 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Mon, 22 Nov 2010 12:13:18 +0000 Subject: [PATCH] Clarified the text describing the deprecation status of mod_python. Thanks to mattmcc and Tai Lee for pointing out the ambiguity. git-svn-id: http://code.djangoproject.com/svn/django/trunk@14679 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.3.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt index fc482b27b4..eea75470f6 100644 --- a/docs/releases/1.3.txt +++ b/docs/releases/1.3.txt @@ -334,9 +334,12 @@ of active projects in its version control repositories, and its lead developer has shifted all of his efforts toward the lighter, slimmer, more stable, and more flexible ``mod_wsgi`` backend. -If you are currently using the ``mod_python`` request handler, it is strongly -encouraged you redeploy your Django instances using :doc:`mod_wsgi -`. +If you are currently using the ``mod_python`` request handler, you +should redeploy your Django projects using another request handler. +:doc:`mod_wsgi ` is the request handler +recommended by the Django project, but :doc:`FastCGI +` is also supported. Support for +``mod_python`` deployment will be removed in Django 1.5. Function-based generic views ~~~~~~~~~~~~~~~~~~~~~~~~~~~~