> > Communication. > > From a purist theoretical perspective, there shouldn't be any argument - > the data we're talking about is a list. Lists have homogeneous elements; > Tuples have heterogeneous elements, but have *positional* homogeneity. A > "Point" is a tuple, because element 0 of the tuple "means" the x > coordinate. A Database row is a tuple - The first element is the primary > key (an integer), second is the "name" column (a string), and so on. > > A tuple is *not* "just an immutable list". > So maybe we should be using lists instead of tuples in our list_display docs? https://docs.djangoproject.com/en/1.6/intro/tutorial02/#customize-the-admin-change-list
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/434a313e-3226-4a2f-9209-1454f6299c82%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
