Hello site
[auf_framonde.git] / eggs / Django-1.4.5-py2.7.egg / django / conf / project_template / project_name / wsgi.pyc
1\ 3ó\r
2ez[Tc\0\0\0\0\0\0\0\0\ 3\0\0\0@\0\0\0sB\0\0\0d\0\0Z\0\0d\ 1\0d\ 2\0l\ 1\0Z\ 1\0e\ 1\0j\ 2\0j\ 3\0d\ 3\0d\ 4\0\83\ 2\0\ 1d\ 1\0d\ 5\0l\ 4\0m\ 5\0Z\ 5\0\ 1e\ 5\0\83\0\0Z\ 6\0d\ 2\0S(\ 6\0\0\0s\99\ 2\0\0
3WSGI config for {{ project_name }} project.
5This module contains the WSGI application used by Django's development server
6and any production WSGI deployments. It should expose a module-level variable
7named ``application``. Django's ``runserver`` and ``runfcgi`` commands discover
8this application via the ``WSGI_APPLICATION`` setting.
10Usually you will have the standard Django WSGI application here, but it also
11might make sense to replace the whole Django WSGI application with a custom one
12that later delegates to the Django one. For example, you could introduce WSGI
13middleware here, or combine a Django application with an application of another
16iÿÿÿÿNt\16\0\0\0DJANGO_SETTINGS_MODULEs\e\0\0\0{{ project_name }}.settings(\ 1\0\0\0t\14\0\0\0get_wsgi_application(\a\0\0\0t\a\0\0\0__doc__t\ 2\0\0\0ost\a\0\0\0environt
17\0\0\0setdefaultt\10\0\0\0django.core.wsgiR\ 1\0\0\0t\v\0\0\0application(\0\0\0\0(\0\0\0\0(\0\0\0\0sd\0\0\0/srv/marc/auf_framonde/eggs/Django-1.4.5-py2.7.egg/django/conf/project_template/project_name/wsgi.pyt\b\0\0\0<module>\ f\0\0\0s\b\0\0\0\ 6\ 1\f\ 2\13\ 5\10\ 1