Ticket #16663: 16663-docs.patch

docs/ref/models/fields.txt

@@ -146 +146 @@
 :meth:`~django.db.models.Model.get_FOO_display` in the database API
 documentation.
 
-Finally, note that choices can be any iterable object -- not necessarily a list
-or tuple. This lets you construct choices dynamically. But if you find yourself
-hacking :attr:`~Field.choices` to be dynamic, you're probably better off using a
-proper database table with a :class:`ForeignKey`. :attr:`~Field.choices` is
-meant for static data that doesn't change much, if ever.
+Finally, note that choices can be any non-empty iterable object -- not
+necessarily a list or tuple. This lets you construct choices dynamically. But if
+you find yourself hacking :attr:`~Field.choices` to be dynamic, you're probably
+better off using a proper database table with a :class:`ForeignKey`.
+:attr:`~Field.choices` is meant for static data that doesn't change much, if
+ever.
 
 ``db_column``
 -------------