> Not really. Anything you can do to a tuple (which is, basically, > iterate over it, slice it and access specific items out of it) you can > also do to a list. A tuple is just a little bit more efficient when > you know you're dealing with something that isn't/shouldn't be > mutable.
Actually, I think "list_per_page" should be an integer, not a list as it is on the cheat sheet. If so, that means only the js option is a list. Which means everything that has a multiple option list is a tuple already, with the exception of the js list. For some reason I thought ordering took a list. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
