Agreed, I'm +1 to keeping deprecated settings inline rather than moving 
them to their own section, but I'd defer to whoever made the original 
decision.

On Tuesday, January 8, 2013 4:58:17 AM UTC-5, Sam Lai wrote:
>
> Looks good. Adds a bit more structure for browsing but doesn't 
> significantly change how the page is used, which is probably through 
> CTRL-F. 
>
> As mentioned by others in the issue, the distinction current and 
> deprecated settings seems very arbitrary. I think it'll be better to 
> sort the deprecated settings like any other setting, but include a 
> better visual distinction to indicate that they're deprecated (at 
> least bold the word deprecated I think). When someone's looking for a 
> setting, they're not thinking about whether or not a setting is 
> deprecated; they're probably looking for what it means and how it can 
> be configured. 
>
>
>
> On 8 January 2013 08:02, Tim Graham <[email protected] <javascript:>> 
> wrote: 
> > I'd appreciate feedback on #14633 - "Organize settings reference docs". 
> So 
> > far I've broken out the settings for each contrib app into their own 
> > sections. The one comment on the pull request suggests further breaking 
> up 
> > the settings listed in the "Core settings" section, e.g. logging, 
> caches, 
> > globalization (i18n/l10n), email, file uploads/media, storages, and 
> > security. I don't feel strongly about this proposal: it could be useful, 
> but 
> > it could also be ambiguous as to which section a particular settings 
> belongs 
> > in. 
> > 
> > The pull request also suggests organizing the default settings.py in a 
> > similar fashion.  While it may be outside of the scope of this ticket, 
> it 
> > could be worthwhile to discuss that suggestion as well. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Django developers" group. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/django-developers/-/Uku6Vo8oCvIJ. 
> > To post to this group, send email to 
> > [email protected]<javascript:>. 
>
> > To unsubscribe from this group, send email to 
> > [email protected] <javascript:>. 
> > 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 view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/WZWRDsCUqFcJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to