On 2/12/06, limodou <[EMAIL PROTECTED]> wrote: > > I don't want to touch this subject more. If you don't understand I'll > explain it again:
I think we understand what you're saying; the problem is that we don't agree. ;-) As others have pointed out, it is perfectly acceptable to create your own configuration files, in your own custom format for your automated tool, and have the Django config modules read them in. Once you set up the Django config modules properly to do this, you would never have to touch them again (barring backwards-incompatible changes or whatnot -- and maybe not even then, depending on how you set things up). Where we run into an issue is your request for such a mechanism to be foisted upon Django itself; as the string of -1 comments thus far indicates, we specifically *want* and *prefer* Django's config files to be Python modules. Again, this does not in any way stop you from implementing your solution; we just aren't going to make it part of Django proper. :-)
