If a user puts a single pair of field names in unique_together, they'll get something looking like this traceback when they try to install the application:
Traceback (most recent call last):
File "C:\dev\django-svn\django\core\management.py", line 389, in install
sql_list = get_sql_all(mod)
File "C:\dev\django-svn\django\core\management.py", line 261, in get_sql_all
return get_sql_create(mod) + get_sql_initial_data(mod)
File "C:\dev\django-svn\django\core\management.py", line 88, in get_sql_create
table_output.append('UNIQUE (%s)' % \
File "C:\dev\django-svn\django\core\meta\__init__.py", line 393, in get_field
raise FieldDoesNotExist, "name=%s" % name
django.core.meta.FieldDoesNotExist: name=f
The user might waste a lot of time figuring out that the reason for this is that they specified ('field1', 'field2') or (('field1', 'field2')) rather than (('field1', 'field2'),) or [('field1', 'field2')].
