diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-10-05 09:00:07 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2008-10-05 09:00:07 +0000 |
| commit | 5da08047b9ff074173e6a3dc6c9b5d5a03c89bf5 (patch) | |
| tree | ff02c5c5d68e18987195670edabf94c9d06dd07e /docs | |
| parent | 9b5c2293c647967e42b320109f32f77b01d6a3aa (diff) | |
[1.0.X] 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.
Backport of r9146 from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9147 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/settings.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/topics/settings.txt b/docs/topics/settings.txt index d9c8f0ab62..16f80d5312 100644 --- a/docs/topics/settings.txt +++ b/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 |