As far as a solution that "magically solves everyone's problem nicely", that's what django-appsettings<http://github.com/jabapyth/django-appsettings>is trying to be :). It handles quite nicely the issues of scoping and maintainability that you discussed, organizing everything in a pythonic manner.
Jared On Wed, Mar 10, 2010 at 7:51 AM, Brian Rosner <bros...@gmail.com> wrote: > > On Mar 10, 2010, at 7:16 AM, Joan Miller wrote: > > > It's a disaster from the maintenance view point. If it were not so, > > then people would not be proposing to refactor the settings as has > > been made in Pinax, or from multiple posts so many times. > > Like I mentioned in the post you made to the pinax-core-dev mailing list > the problem Pinax is trying to solve is *not* because the settings are > written in Python, but rather loading order and scope. Many projects quickly > realize that running a Django project with a single settings file is nearly > impossible with different environments all interacting with a single code > base. Some projects turn to importing a local_settings.py file which is what > Pinax currently does. This has worked wonderful for us for years. However, > there has always been a scoping issue. It was difficult to easily change > settings defined at the "global" level (this being project-wide settings > that are environment agnostic). You'd have to copy them to the > local_settings.py and add in extra values or remove existing values. One > approach to solve this problem is to flip the loading order (imports happen > at the settings.py level including the project level settings). While this > works it presents a problem to usability. It would require an extra step on > behalf of the user to either copy or create a missing settings file to run. > This was a non-starter in Pinax since a fundamental goal is to get up and go > once you've created the project. We've ultimately ended up on the solution > Carl gave which can be read on our mailing list. > > I don't see how your YAML configuration solves any of these problems. You'd > have to create a similar mechanism with where you parse YAML files and then > you are solving the same problem we are. If there is a solution you have in > mind that magically solves everyone's problem nicely then present that > instead of hand waving. > > Brian Rosner > http://oebfare.com > http://twitter.com/brosner > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
