Setting other types than `int` to `range.index()` gets the less clear different error messages

[hyperkai]

Bug report

Bug description:

Setting int to range.index() gets the clear error message as shown below:

v = range(5)

print(*v)
# 0 1 2 3 4

print(v.index(7))
# Error

ValueError: 7 is not in range

But setting other types than int to range.index() gets the less clear different error messages as shown below:

v = range(5)

print(*v)
# 0 1 2 3 4

print(v.index(7.5))
print(v.index(7.5+0.0j))
print(v.index('A'))
# Error

ValueError: sequence.index(x): x not in sequence

So they should also be as shown below:

ValueError: 7.5 is not in range
ValueError: 7.5+0.0j is not in range
ValueError: 'A' is not in range

CPython versions tested on:

3.12

Operating systems tested on:

Windows

[skirpichev]

Same happens for int's subclasses:

>>> class int2(int):
...     pass
... 
>>> v.index(int2(7))
Traceback (most recent call last):
  File "<python-input-7>", line 1, in <module>
    v.index(int2(7))
    ~~~~~~~^^^^^^^^^
ValueError: sequence.index(x): x not in sequence

In this case (non-int/bool) we just fallback to _PySequence_IterSearch().

the less clear different error messages

Could you explain this? The v is a sequence:

>>> import collections
>>> isinstance(v, collections.abc.Sequence)
True

This is documented too:

The range type represents an immutable sequence of numbers

[picnixz]

This is very similar to #137508 so please avoid creating similar issues when there is one. Just comment on the existing issue if you find other similar cases.

[skirpichev]

please avoid creating similar issues when there is one

IMO, I don't think this is the major issue with this report.

Lack of any explanation (why it's an issue at all?), unfortunately, too common for @hyperkai's bugs.