I was thinking the decorator could apply to whatever setting is declared directly following it. If declared, the setting simply wouldn't show up. However I could add SECRET or PASSWORD to my token sensitive settings just as well.
On Jan 31, 7:00 pm, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Tue, Feb 1, 2011 at 12:12 AM, Horst Gutmann <ho...@zerokspot.com> wrote: > > On Mon, Jan 31, 2011 at 5:02 PM, Matteius <matte...@gmail.com> wrote: > >> I think it would be really useful to have a way (possibly a decorator > >> such as @hide_setting) such as to protect deployed sites when they > >> switch over to debug mode. To me this would be a most useful setting > >> to have, especially when protecting secret key settings. Please be > >> advised. > > > If I remember correctly, settings starting with SECRET_ are not shown > > on the debug page. > > Not completely correct. There is a list of settings that won't be > displayed -- anything that contains the text > SECRET, PASSWORD, PROFANITIES_LIST, or SIGNATURE will be replaced > with asterisks. It's not an unreasonable suggestion that this list > should be user-configurable. > > As for the original proposal - I'm not sure how a decorator would help > here. What is the decorator being applied to? What would the decorator > indicate? How would that information be exposed to the debug view? > > Yours, > Russ Magee %-) -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
