>You mean that you'll never want to change them. And I also made a
>seconad topic about this, it's seem that you didn't notice it. What I
>want just want to make django more easiler for installation,
>deployment, or somethings. Have you some good suggestions about how to
>simplify the changing of configuration files programmatically always
>welcome.

Django _is_ easy to install and deploy. And it won't get easier by your
proposal - actually it would make it harder and more complicated for
people who prefer to compute setting values (which is allmost allways
the case with my project structure, for example).

But if you want to have an environment where you don't set settings
directly in python code but from some external config file, just write
functions to do that (manage that settings file) and use those
functions in your settings.py to populate it's namespace. There is no
one preventing to go that way.

You seem to be fixed on the idea that your tools must manage a file
named "settings.py" - they don't need to, they can manage a file
"settings.txt" and that can be used in your settings.py to pull in
settings (for example using globals()). That way you would install a
Django app and a standard settings.py that would just pull in stuff
that's managed outside, if you want to do it that way. settings.py
could look something along this in your configuration:

import configthingy

for k,v in configthingy.parse('settings.txt'):
   globals()[k] = v

That way your settings.py will be populated from some outside source
and that outside source could be managed however you want to.

Your proposal on the other hand would _take_away_ some freedom from
Django programmers and so you hit the wall of -1 quite hard. The
comments to your proposal should show you that you won't get _that_
idea through. If you do it the other way around, your tools just become
another way to do project configuration and people might or might not
adopt it - but without any need of changes to Django, you can do it
alongside django as your own project.

bye, Georg

Reply via email to