BUG: Do not try sequence repeat unless necessary

Only if the other class actually implements sequence repeat, should
it be tried. Otherwise classes which implement neither will cause
the sequence repeat branch. This branch may fail for two reasons:
 1. The scalar was not integer
 2. The other object raises an error during repeat.

Previously, the first did not happen for floats, etc. and the
second was using a try/except logic. Now both will always error.
An object which claims to support sequence repeat should never
have to fall back to normal multiplication.

Note that all of this is controversial in the final behaviour.
We may actually want `[1, 2, 3] * np.float64(3.)` to return
an array with `[3., 6., 9.]` at some point.

-

It was suggested to create a better error message, this
is not covered here. The major point is fixed though, so:
closing gh-7428

0 files changed, 0 insertions, 0 deletions