On Mon, Nov 3, 2008 at 7:01 PM, pk <[EMAIL PROTECTED]> wrote: > James is right that for any of my own app, I can just tell the user > to put in some settings in the project level settings.py file. In fact > that is exactly what I do now.
And that is what quite a number of popular third-party Django applications -- every one of them intended to be used and reused -- are doing. I don't really see a need for some system of forcing default values, since in many cases *not* supplying an explicit value for such a setting is an error (because not supplying it *or* falling back to a default can break the application or cause undesired behavior). Much better to simply document what's needed, and rely on the fact that trying to run without setting it will raise an error. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
