Re: dynamically assigning settings on startup with wsgi

2009-02-03 Thread felix
nevermind

moral: if it seems illogical it probably is something else


On Wed, Feb 4, 2009 at 12:38 AM, felix  wrote:

>
> adict = {
>   'DATABASE_PASSWORD' : "something"
> }
>
> in settings.py :
>
> locs = vars()
> for key,value in adict:
> locs[key] = value
>
> I'm dynamically assigning variables in settings
>
> this works in the development server (a wsgi), but NOT on the production
> server using mod_wsgi
>
> is there a known difference or reason why this should not work ?
>
> thanks
>
>  felix :crucial-systems.com
>
>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---



dynamically assigning settings on startup with wsgi

2009-02-03 Thread felix
adict = {
  'DATABASE_PASSWORD' : "something"
}

in settings.py :

locs = vars()
for key,value in adict:
locs[key] = value

I'm dynamically assigning variables in settings

this works in the development server (a wsgi), but NOT on the production
server using mod_wsgi

is there a known difference or reason why this should not work ?

thanks

 felix :crucial-systems.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---