From 54887d686b1552ae98e3eb4fa57a64036eea72a5 Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Tue, 22 Jan 2013 16:15:52 -0500
Subject: [PATCH] [1.5.x] Fixed #19633 - Discouraged use of gunicorn's Django
 integration.

Backport of 0db86273ae from master
---
 docs/howto/deployment/wsgi/gunicorn.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/howto/deployment/wsgi/gunicorn.txt b/docs/howto/deployment/wsgi/gunicorn.txt
index c4483291a3..14c80af0a0 100644
--- a/docs/howto/deployment/wsgi/gunicorn.txt
+++ b/docs/howto/deployment/wsgi/gunicorn.txt
@@ -48,6 +48,12 @@ ensure that is to run this command from the same directory as your
 Using Gunicorn's Django integration
 ===================================
 
+.. note::
+
+    If you are using Django 1.4 or newer, it’s highly recommended to simply run
+    your application with the WSGI interface using the ``gunicorn`` command
+    as described above.
+
 To use Gunicorn's built-in Django integration, first add ``"gunicorn"`` to
 :setting:`INSTALLED_APPS`. Then run ``python manage.py run_gunicorn``.