From 91f4a75a6b83c51aae7318d6aec4e5557ffe42ff Mon Sep 17 00:00:00 2001
From: Claude Paroz <claude@2xlibre.net>
Date: Mon, 24 Feb 2014 18:26:29 +0100
Subject: [PATCH] Fixed #22116 -- Added precision about WSGIPythonPath
 separator

Thanks donjpacheco for the initial patch.
---
 docs/howto/deployment/wsgi/modwsgi.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/howto/deployment/wsgi/modwsgi.txt b/docs/howto/deployment/wsgi/modwsgi.txt
index a04d35a23a..be73c8f625 100644
--- a/docs/howto/deployment/wsgi/modwsgi.txt
+++ b/docs/howto/deployment/wsgi/modwsgi.txt
@@ -74,7 +74,10 @@ Using a virtualenv
 If you install your project's Python dependencies inside a `virtualenv`_,
 you'll need to add the path to this virtualenv's ``site-packages`` directory to
 your Python path as well. To do this, add an additional path to your
-`WSGIPythonPath` directive, with multiple paths separated by a colon::
+``WSGIPythonPath`` directive, with multiple paths separated by a colon (``:``)
+if using a UNIX-like system, or a semicolon (``;``) if using Windows. If any
+part of a directory path contains a space character, the complete argument
+string to ``WSGIPythonPath`` must be quoted::
 
     WSGIPythonPath /path/to/mysite.com:/path/to/your/venv/lib/python2.X/site-packages