WSGI-script produces a different path than the management wrapper

[Horst Gutmann]

I ran into a small problem where the order of the sys.path components was relevant and I noticed that the generated django.wsgi script appends the local components while bin/django prepends them. IMO local path components should be prepended in both cases.

Tested with zc.buildout 1.2.1

[Jacob Kaplan-Moss (jacobian)]

This is more than just a consistency thing. Because the WSGI script uses sys.path.extend it means that buildout-installed dependencies get overridden by system-wide packages, and this makes djangorecipe-based deployments hard or impossible in shared hosting situations.

As an example, my particular situation is a host with lxml 1.3 installed but a deployment that needs lxml 2.2. The 2.2 egg is installed just fine, but because the WSGI script extends the path the systemwide 1.3 egg is always loaded instead.

[Jannis Leidel (jezdez)]

Jacob is totally right, the global site-packages will override the packages installed by buildout. I've fixed that in my branch by using buildout's own mechanism to create script files so it's guaranteed to be the same path as in the manage script. This is a critical bug, IMO.