str() of a tuple

[Brian Quinlan]

> Why, oh why does the str() of a container use the repr()s of the
> objects inside?  This seems to violate what the docs claim str() does
> -- "return a nicely printable representation of an object."  Would a
> sane implementation break something?

(Before I tell you, could you please tell me what this tuple contains? I
bet that you can't figure it on in less than, say, 5, days)

Cheers,
Brian