This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author schen
Recipients brett.cannon, llllllllll, rhettinger, schen
Date 2017-05-26.08:32:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495787579.66.0.864003261638.issue30477@psf.upfronthosting.co.za>
In-reply-to
Content
What is the rationale for the inconsistency between tuples and lists here?

().index(0)
ValueError: tuple.index(x): x not in tuple

[].index(0)
ValueError: 0 is not in list

In this simple artificial case, it seems clear to me that the list version (which is similar to the proposed change) is superior.

However, it is often not sufficient to use such cases as the basis for making a decision. Raymond raises some very good points.

In particular, I noticed that printing the repr quickly becomes unwieldy for more complex objects. For example, I tried the following:
[].index(''.join(chr(randrange(97, 97+26)) for _ in range(1000)))
[].index(Counter(randrange(10) for _ in range(10000)))
History
Date User Action Args
2017-05-26 08:32:59schensetrecipients: + schen, brett.cannon, rhettinger, llllllllll
2017-05-26 08:32:59schensetmessageid: <1495787579.66.0.864003261638.issue30477@psf.upfronthosting.co.za>
2017-05-26 08:32:59schenlinkissue30477 messages
2017-05-26 08:32:59schencreate