On 8/7/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > The thing is, there's no foolproof distinction between what settings > should differ for dev environments and which ones are definitely for > production environments. You gave the examples of MIDDLEWARE_CLASSES > and ROOT_URLCONF, but those settings are almost always different > between dev and production for my own personal projects. Point is, > every developer is different, and we shouldn't waste the time in > trying to come up with some sort of framework on top of the settings > framework.
Fair enough, but this isn't terribly different from how settings.py overrides django defaults. You've just moved it down to the project level. I don't think specifying project defaults and then user settings requires a whole new framework. It's basically what you already have going on. Django defaults -> settings.py -> user_settings.py With entries to the right overriding all those to the left. > If you and your development team find yourselves duplicating settings, > by all means factor them out into a common, shared settings file. Indeed, that's what we ended up doing. I'm sure we've done it differently than most others have. What's lacking is consistency to a common problem. It's nice to talk about individuality, but when I look at someone else's code, I have to put more thought into how settings are overridden than is really necessary. Is it a lot? Probably not. Is it unnecessary? I believe so. Ignoring the problem doesn't really help anyone out. I've pitched my idea above, but at the least I still think a note in the documentation, which implicitly endorses a particular method, would cut down on the number of times the question arises and otherwise ambiguity. If you still disagree, then I guess we'll just have to agree to disagree and I'll begrudgingly drop the matter. -- Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
