True, I did notice it needed some more tweaking. I've got a long evening of 
rewriting years' worth of wsgi.py's and Apache configs ahead of me. I'll 
probably just jump straight to the envparse approach because (as you noted) 
my celery env var handling was making the WSGI approach moot anyway.

Now if there were only a way to avoid having to put 
os.environ["DJANGO_SETTINGS_MODULE"] = "myapp.settings" into wsgi.py (since 
I'm sharing lots of vhosts in one Apache) ...

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/9bab5139-ea38-418e-8b97-c49463be65e3%40googlegroups.com.

Reply via email to