On 2/10/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 2/9/06, limodou <[EMAIL PROTECTED]> wrote: > > I'v summited a ticket http://code.djangoproject.com/ticket/1337 for this. > > > > What do you think about? > > I marked that ticket as a wontfix yesterday. Respectfully, let me just > say that it's not going to happen. As I implied in the ticket, there's > nothing stopping you from writing your own machinery that creates a > settings file by reading plain text, parsing XML, performing OCR on > scanned paper documents, or analyzing audio clips of you reciting the > settings.
But there is not a standard interface to do that. And most of the them need I change these things manually. Even though I'v finished two modules for doing that programatically, but I want to know if django can provide a standard interface for doing these things. If there is no, I'll using my hacking way continually. > > That's the nice thing about having the settings in Python: You can do > whatever you need to do. I agree. But it's not so easy for doing it programatically, expecially for saving it just like the original files style, for example, saving comments in settings.py. > > Let's move onto other ideas and decisions! > > Adrian > As you say that I won't insist more. Thanks all of your patience. -- I like python! My Blog: http://www.donews.net/limodou NewEdit Maillist: http://groups.google.com/group/NewEdit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
