On Wednesday 20 January 2010 17:15:39 sago wrote:

> Startup and Settings are the big killers though, head and shoulders
> above the previous issues. I've nothing much to add to your
>  comments other than to say that some of the Django deployments I
>  know of are highly heterogeneous, with various servers running
>  different SOA elements, some Django some not. The configuration
>  issues are formidable and involve all kinds of dependencies beyond
>  Django (or even Python). I struggle to see a way that Django could
>  solve those issues, but allowing more flexibility and avoiding
>  tying configuration to an executable module (i.e. settings.py)
>  would be useful. 

I don't understand how avoiding the settings.py mechanism will produce 
*more* flexibility.  With an executable module storing settings, you 
can implement whatever mechanism you want for settings:

## settings.py ##

import sys
from acme import network_config

network_config.load_django_settings_into_module(sys.modules[__name__])

## end.

Granted, code that does the above might need to be written, but the 
point of settings.py is that you *can* write it, without forcing 
anyone to use that system.

Luke

-- 
"Procrastination: Hard work often pays off after time, but laziness 
always pays off now." (despair.com)

Luke Plant || http://lukeplant.me.uk/

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


Reply via email to