On 2/13/06, Tom Tobin <[EMAIL PROTECTED]> wrote: > > 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). > Is that true? I'v assume many scenes just like in development period, I need install others apps or in deployment period I need reinstall many new apps also. So the settings.py and urls.py will not always unchanged. But if django has some configuration customization support, this aim will be reached.
> 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. :-) > So maybe django project should design a pattern that either remaining the python config files, or simplifying the customization of the configuration to automatic tools. And I want to know if such automatic tools is useful to django? Or if people need these tools to help them? Thanks. -- I like python! My Blog: http://www.donews.net/limodou NewEdit Maillist: http://groups.google.com/group/NewEdit
