On 2/10/06, limodou <[EMAIL PROTECTED]> wrote: > Maybe you consider that it's nothing, so I think you also don't want a > tool to do that for you automatically. But I want, and I think maybe > someone else want also.
What, exactly, is it about Python files which make it, in your view, unreasonably difficult to automate the process? If anything, having the settings in Python should mean that it's *easier* to automate, because you can load the settings file as Python and manipulate items in it natively. > libraries, etc. And also everyone need to install this app also need > to these things. And if I'v finished my project, I'll need install > them to online server, but maybe I cann't just copy all files to the > online server, so maybe I need install the apps to online server. What, right at this moment, is stopping you from being able to write tools which do these things? Why would the format of the files matter to a script whose purpose is to upload a set of files and run a command on the server when that's done? > Do you want these? Why not make a tool for that? That's why I need > more simple automatic support supplied by django. And maybe someone or > something else also need these mechanism, just like an Editor? Django provides enough automation right now, in my opinion. If you need or want more automation, I don't see anything that's getting in the way of your being able to write more automation tools for your own use, least of all the file format of Django's configuration. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
