Author: russellm
Date: 2010-11-22 06:13:18 -0600 (Mon, 22 Nov 2010)
New Revision: 14679

Modified:
   django/trunk/docs/releases/1.3.txt
Log:
Clarified the text describing the deprecation status of mod_python. Thanks to 
mattmcc and Tai Lee for pointing out the ambiguity.

Modified: django/trunk/docs/releases/1.3.txt
===================================================================
--- django/trunk/docs/releases/1.3.txt  2010-11-22 06:44:59 UTC (rev 14678)
+++ django/trunk/docs/releases/1.3.txt  2010-11-22 12:13:18 UTC (rev 14679)
@@ -334,9 +334,12 @@
 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
-</howto/deployment/modwsgi>`.
+If you are currently using the ``mod_python`` request handler, you
+should redeploy your Django projects using another request handler.
+:doc:`mod_wsgi </howto/deployment/modwsgi>` is the request handler
+recommended by the Django project, but :doc:`FastCGI
+</howto/deployment/fastcgi>` is also supported. Support for
+``mod_python`` deployment will be removed in Django 1.5.
 
 Function-based generic views
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to