Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Changed the "write your own settings" recommendation to mention that …

…Django

uses tuples, but not making it a recommendation. That might head off the endless
tuples vs. lists debates.

Fixed #8846.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@9146 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 806ea3a1dede8d51df11c2bd9c2f23be95ea6e00 1 parent e1b7211
@malcolmt malcolmt authored
Showing with 3 additions and 2 deletions.
  1. +3 −2 docs/topics/settings.txt
View
5 docs/topics/settings.txt
@@ -160,10 +160,11 @@ There's nothing stopping you from creating your own settings, for your own
Django apps. Just follow these conventions:
* Setting names are in all uppercase.
- * For settings that are sequences, use tuples instead of lists. This is
- purely for performance.
* Don't reinvent an already-existing setting.
+For settings that are sequences, Django itself uses tuples, rather than lists,
+but this is only a convention.
+
.. _settings-without-django-settings-module:
Using settings without setting DJANGO_SETTINGS_MODULE

0 comments on commit 806ea3a

Please sign in to comment.
Something went wrong with that request. Please try again.