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.
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.