I disagree... You can organizate the information of settings.txt in other manner, with a essential settings, and non-essential settings (or insignificant settings, as you say) and fix the problem.
But, indeed, is better providing to developer two ways of setting his develop environment (with option or setting), and avoid to enforce making a start.sh script with --admin-media option. Regards, Lin El lun, 25-09-2006 a las 07:36 +1000, Malcolm Tredinnick escribió: > On Sun, 2006-09-24 at 16:11 +0200, Manuel Saelices wrote: > > Hi all, > > > > I just look 3811 revision... tha patch makes posible you can run > > development server with: > > > > ./manage.py runserver --adminmedia /foo/path/ > > > > It is a good idea, but I think it can be done besides with a > > ADMIN_MEDIA_DIR (or ADMIN_MEDIA_ROOT) setting, instead of have to > > remember runserver with that option. > > Look at the ticket that change was addressing (#2600). The patch > submitted there originally used a setting and Adrian pointed out that it > was a bit of overkill for an edge case like the development server. I > agree with Adrian's logic here: we do have to be a bit careful about > just making everything a setting, since otherwise the important settings > get lost in amongst the documentation for all the relatively > insignificant settings. > > Regards, > Malcolm > > > > -- Manuel Saelices [EMAIL PROTECTED] ICS Yaco S.L. http://www.yaco.es/ Tlfno. +34 954 50 00 57 Fax +34 954 50 09 29 C/ Sierpes, 48 Sevilla --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
