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
This commit is contained in:
parent
6482dec295
commit
cbd90455a0
|
@ -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
|
has shifted all of his efforts toward the lighter, slimmer, more stable, and
|
||||||
more flexible ``mod_wsgi`` backend.
|
more flexible ``mod_wsgi`` backend.
|
||||||
|
|
||||||
If you are currently using the ``mod_python`` request handler, it is strongly
|
If you are currently using the ``mod_python`` request handler, you
|
||||||
encouraged you redeploy your Django instances using :doc:`mod_wsgi
|
should redeploy your Django projects using another request handler.
|
||||||
</howto/deployment/modwsgi>`.
|
: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
|
Function-based generic views
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
Loading…
Reference in New Issue