Idiomatic Python: use lists instead of tuples where appropriate

[Patryk Zawadzki]

Currently most of the documented lists are actually tuples. This is uncalled for and not really pythonic.

Python authors have already stated that tuple was not a frozen list. Let's stick to using tuples where tuples fit, eg. where a namedtuple could be used instead but would be an overkill.

[Patryk Zawadzki]

Pull request: ​https://github.com/django/django/pull/1177

[Marc Tamlyn]

I'm concerned about the backwards compatibility of this patch - I know in a number of my projects I import the default value from global settings and combine it with another list/tuple of my own appropriately. It's a minor issue, but I'm not sure it's worth breaking things for the sake of a little properness. Nothing is broken at the moment.

[Patryk Zawadzki]

@mjtamlyn, can you provide a case that no longer works?

[Tim Graham]

I had similar concerns. For example:

from django.conf.global_settings import TEMPLATE_CONTEXT_PROCESSORS
TEMPLATE_CONTEXT_PROCESSORS + ('myapp.myprocessor',)

After this change, the above code would throw an error: TypeError: can only concatenate list (not "tuple") to list.

[Aymeric Augustin]

Like Marc and Tim, I don't think the disruption caused by this change is really worth it.