On Oct 11, 9:05 am, Carl Meyer <[email protected]> wrote: > What's the impact on adding a standard WSGI entrypoint? > - ------------------------------------------------------- > > #16360 [5] has a patch to add a "wsgi.py" file to the default project, > which will serve as a standard WSGI entrypoint that can be used both by > runserver and by production WSGI servers. I love the idea and the patch > - - except that its approach to easing the deployment path is to extend > the current sys.path-hacking of setup_environ beyond just manage.py and > into every WSGI deployment. > > But if we first fix the sys.path-hacking as I propose, the wsgi.py file > will go next to manage.py in the default project layout. Since WSGI > servers chdir() to the directory of the wsgi file you point them at, no > sys.path additions (whether manually or magically in Django) will be > needed in order to deploy a Django project under a production WSGI > server. Again, win.
Apache/mod_wsgi does not change the current working directory to be where the WSGI file is located so that will not work for Apache/ mod_wsgi. A sys.path modification would still be need. Graham -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
