In article <[EMAIL PROTECTED]>, "Hendrik van Rooyen" <[EMAIL PROTECTED]> wrote:
> "Donn Cave" <[EMAIL PROTECTED]> wrote: > > > > > Well, yes - consider for example the "tm" tuple returned > > from time.localtime() - it's all integers, but heterogeneous > > as could be - tm[0] is Year, tm[1] is Month, etc., and it > > turns out that not one of them is alike. The point is exactly > > that we can't discover these differences from the items itself - > > so it isn't about Python types - but rather from the position > > of the item in the struct/tuple. (For the person who is about > > to write to me that localtime() doesn't exactly return a tuple: QED) > > This is the point where the whole thing falls apart in my head and > I get real confused - I can't find a reason why, list or tuple, the first > item can't be something, the second something else, etc... Of course, you may do what you like. Don't forget, though, that there's no "index" method for a tuple. Donn Cave, [EMAIL PROTECTED] -- http://mail.python.org/mailman/listinfo/python-list
