On 2/9/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > On 2/10/06, limodou <[EMAIL PROTECTED]> wrote: > > > > I'v summited a ticket > http://code.djangoproject.com/ticket/1337 for this. > > > > What do you think about? > > -1 from me.
I second that -1; by the logic in that ticket, we might as well rewrite the module definitions in a config.ini format since end users might want to fiddle with the modules in a given deployed app. :-p Seriously, though, I don't see Python's syntax as an obstacle for casual config tweaking. I'm guessing the use-case in the ticket is concerned with those who might someday be making use of Django with ready-to-run plug-in applications (whether from django.contrib or third parties), with little concern for playing with models, views, and the like. A basic settings.py is nothing but variable assignments with strings and tuples; as for urls.py, plug-in apps will likely handle all the heavy regex lifting on their own end, leaving the installing user to drop a simple include line into the file. I'm not sure if a user who isn't comfortable doing even that much should be installing Django on their own. ;-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
