dbsettings, and user configurable app settings

I have been looking around for a way of managing user-configurable application settings, and the only solution I have found is dbsettings, which looks like it hasn't been touched in 3 years. So, I would like to know: is dbsettings dead? Or is there a different generally accepted method for having u

Re: dbsettings, and user configurable app settings

lied/adapted to some later > version of django. That might be a place to apply some development if > anyone is interested in working towards better settings management. > > http://groups.google.com/group/pinax-core-dev/browse_thread/thread/d9401468ea3c8edf > > -Wes > &

Re: dbsettings, and user configurable app settings

I'm currently working on a solution to this which I call appsettings, and I think it addresses many of the concerns raised here. appsettings loads your module's settings.py in much the same way that contrib.admin loads your admin.py, and you call appsettings.register (can be used as a decorator) to

2 small tickets

I found some bugs, wrote come patches, submitted some tickets. =) Is that all that's needed? The two patches I wrote are *very* small, one is only one char diff... I guess I just want to know a) have I done all that's required/suggested, and b) if so, what's the expected turnaround time for very sm

Re: 2 small tickets

ssell Keith-Magee wrote: > On Wed, Mar 3, 2010 at 3:41 PM, Jared Forsyth > wrote: > > I found some bugs, wrote come patches, submitted some tickets. =) Is that > > all that's needed? > > The two patches I wrote are very small, one is only one char diff... > > I

Re: dbsettings, and user configurable app settings

I think there are some settings which are for the developer, and some which are appropriate for an admin user, who is not necessarily the developer, to have access to. In addition, there are some settings which should be modifiable without necessitating a server restart. There is value in having co

Re: 2 small tickets

2/flatpages_admin_trunk.diff>I ended up with). Thanks Jared On Wed, Mar 3, 2010 at 11:24 AM, Karen Tracey wrote: > On Wed, Mar 3, 2010 at 12:33 PM, Jared Forsyth wrote: > >> As a general "best practices" question: When I update a ticket w/ a test >> case and

Re: Django documentation for newer users

To be honest I am quicker to just go to django's source code rather than the docs, as often I can find what I need there, and the docs aren't (imo) organized enough to provide much of an advantage. On Fri, Mar 5, 2010 at 8:46 AM, stherrien wrote: > Hi all, > > > I have a request that django docu

Re: Easier debugging of Django templates. {% try %} ... {% endtry %} template tag and traceback.

I presume these only get shown with DEBUG turned on? On Fri, Mar 5, 2010 at 9:09 AM, Jonathan S wrote: > Hi Django users, > > We made at our company, City Live, a template tag you may be > interested in. > It's a try/catch statement. When anything in the try block fails, a > traceback through all

Re: Easier debugging of Django templates. {% try %} ... {% endtry %} template tag and traceback.

On a related note, is there a way to tell templates *not* to fail silently? (most tags etc. do) for testing/debugging purposes? jared On Fri, Mar 5, 2010 at 9:53 AM, Jonathan S wrote: > > On Mar 5, 5:49 pm, Jared Forsyth wrote: > > I presume these only get shown with DEBUG turned

Re: dbsettings, and user configurable app settings

It seems like the best place for "project settings"(a) would be applicable is through some ./manage.py command, perhaps "installapps" or something along those lines. This would probably be the place to do database modifications between versions. (b) could be served by a "readonly" flag in the setti

Re: dbsettings, and user configurable app settings

As far as a solution that "magically solves everyone's problem nicely", that's what django-appsettingsis trying to be :). It handles quite nicely the issues of scoping and maintainability that you discussed, organizing everything in a pythonic manner.

Re: Proposal - ChoiceField.choices need to accept callable, not only list or tuple

I say go for it, and post again with a patch and issue number (once you've created them). Your idea seems sound. Jared On Mon, Mar 22, 2010 at 11:30 PM, George Karpenkov wrote: > Hi, > > The subject pretty much describes all of it. If 'initial' can be a > callable, why 'choices' can't? Writing c