p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[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
This commit is contained in:
Malcolm Tredinnick 2008-10-05 09:00:07 +00:00
parent 9b5c2293c6
commit 5da08047b9
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/topics/settings.txt
View File

@ -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