title: Is there any reason not to force sys.path when running with mod_wsgi on apache?
body: <p>So, after getting frustrated one time too many with the path situation under mod_wsgi and apache I took the brute force hammer to it.</p>
  
  <p>Now I'm wondering if there are any possible other pitfalls.</p>
  
  <p>I activated my virtualenv then ran</p>
  
  <pre><code>(virtualenv)$python
  &gt;&gt;&gt; import sys
  &gt;&gt;&gt; for i in sys.path:
  &gt;&gt;&gt;   print "'{}',".format(i)
  &gt;&gt;&gt; quit()
  </code></pre>
  
  <p>then I pasted that into my wsgi file like so:</p>
  
  <pre><code>import sys
  sys.path = [
  
      Block of stuff printed out
  
  ]
  </code></pre>
  
  <p>This way sys.path is the same for apache as it is when I'm running the debug server.</p>
  
  <p>Everything else has always talked about inserting things into the path, Is there some reason this won't just work?</p>
  
  <p>Not that is should matter, but its a django project.</p>