> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:python- > [EMAIL PROTECTED] On Behalf Of Chris Mellon > Sent: Wednesday, April 11, 2007 9:12 AM > To: python-list@python.org > Subject: Re: tuples, index method, Python's design > > > So, when you have a) a third party module that you cannot change and > b) it shouldn't return a tuple but it does anyway and c) it's a big > enough tuple that is large enough that conversion to a list is > prohibitive, that's a "general" use case for tuple.index? > > Has this supposedly general and common use case actually happened?
To me? No. Is it reasonable to believe it could happen? Yes. Is it reasonable to say, "We don't think this is likely to happen often, so we won't provide a simple way to deal with it?" Well, I'm not a developer, so it's not my decision. --- -Bill Hamilton [EMAIL PROTECTED] -- http://mail.python.org/mailman/listinfo/python-list
